3 ms·
This is where it all started. In general, I would agree with you, but the immediate loss of the original elegance and simplicity of the design is obvious. (Also
by Koshkin 10y ago
This is where it all started. In general, I would agree with you, but the immediate loss of the original elegance and simplicity of the design is obvious. (Also, I believe it was a deliberate design decision to only require that the return type be specified - if it is not 'int' - in a declaration of a function. Besides having resulted in easy-to-understand semantics and an uncluttered syntax, this opened a direct way of dealing with an unknown number and/or types of the arguments without needing any additional syntactical "niceties".)
- mpweiher 10y agoYes, the fact that calling conventions changed with prototypes in a way that was incompatible with and could not be duplicated by the existing calling conventions was a mistake. I wrote a little about a very similar case with Objective-C and the default 'id' argument and return type here: http://blog.metaobject.com/2014/03/cargo-cult-typing-or-objective-c.html http://blog.metaobject.com/2014/03/cargo-cult-typing-or-obje...