5 ms·

I personally prefer Prehistoric C, which only has the two language keywords "ugh" and "grunt". Modern C has too many keywords for my taste.

by zunzun 10y ago

oblio 10y ago
> "grunt" I'm sorry, you cannot use this keyword as it will cause a conflict with Javascript tools.
- bitwize 10y ago
  Most people use gulp now -- the reimplementation of the reimplementation of make in JavaScript because reasons.
  - fb03 10y ago
    So true. I'm helping people on a Node App and it was the first time I had to use it to "build" (build what?) the website I should write the API to, lol.
oneeyedpigeon 10y ago
Nah, coming down from the trees was a bad idea: http://www.dangermouse.net/esoteric/ook.html http://www.dangermouse.net/esoteric/ook.html
Koshkin 10y ago
"Prehistoric" or not, the classical C as created by Kernighan and Ritchie is actually a perfect example of a sensibly minimalist design. Subsequent changes made to the language have spoiled the characteristic elegance of that design.
- mpweiher 10y ago
  Well, function prototypes in the first ANSI standard were a fine addition, if you ask me. After that...
  - 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 ago
      Yes, 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...

I personally prefer Prehistoric C, which only has the two language keywords "ugh" and "grunt". Modern C has too many keywords for my taste.

by zunzun 10y ago

I personally prefer Prehistoric C, which only has the two language keywords "ugh" and "grunt". Modern C has too many keywords for my taste.

oblio 10y ago

> "grunt" I'm sorry, you cannot use this keyword as it will cause a conflict with Javascript tools.

bitwize 10y ago
Most people use gulp now -- the reimplementation of the reimplementation of make in JavaScript because reasons.
- fb03 10y ago
  So true. I'm helping people on a Node App and it was the first time I had to use it to "build" (build what?) the website I should write the API to, lol.

oneeyedpigeon 10y ago

Nah, coming down from the trees was a bad idea: http://www.dangermouse.net/esoteric/ook.html http://www.dangermouse.net/esoteric/ook.html

Koshkin 10y ago

"Prehistoric" or not, the classical C as created by Kernighan and Ritchie is actually a perfect example of a sensibly minimalist design. Subsequent changes made to the language have spoiled the characteristic elegance of that design.

mpweiher 10y ago
Well, function prototypes in the first ANSI standard were a fine addition, if you ask me. After that...
- 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 ago
    Yes, 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...