|
| This Article | ||
| | ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
January-March 1984 (vol. 1 no. 1)
pp. 50-61
| ASCII Text | x | ||
| B.J. Cox, "Message/Object Programming: An Evolutionary Change in Programming Technology," IEEE Software, vol. 1, no. 1, pp. 50-61, January-March, 1984. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.1984.233398, author = {B.J. Cox}, title = {Message/Object Programming: An Evolutionary Change in Programming Technology}, journal ={IEEE Software}, volume = {1}, number = {1}, issn = {0740-7459}, year = {1984}, pages = {50-61}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.1984.233398}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Message/Object Programming: An Evolutionary Change in Programming Technology IS - 1 SN - 0740-7459 SP50 EP61 EPD - 50-61 A1 - B.J. Cox, PY - 1984 KW - null VL - 1 JA - IEEE Software ER - | |||
Could a marriage of the message/object model, a la Smalltalk-80, and the operator/operand model, a la Unix, improve the lot of both users and programmers? Stay tuned...
Citation:
B.J. Cox, "Message/Object Programming: An Evolutionary Change in Programming Technology," IEEE Software, vol. 1, no. 1, pp. 50-61, Jan.-March 1984, doi:10.1109/MS.1984.233398
Usage of this product signifies your acceptance of the Terms of Use.

