3 ms·

> I can see the argument for terseness The argument is that my programs are shorter and faster and more correct? > I don't think it's a good idea to use this

by geocar 9y ago

> I can see the argument for terseness The argument is that my programs are shorter and faster and more correct? > I don't think it's a good idea to use this extreme single-character, single-line style in languages not designed for it. You think if I need to write C, that I should do things that make my program larger and slower and less correct? That doesn't make any sense to me at all.

kazinator 9y ago
Longer identifiers don't make C programs larger. (Well, shared libraries have larger symbol tables, and unstripped executables have bigger debug info.) Using multiple lines and indentation doesn't change executable code.
- geocar 9y ago
  > Longer identifiers don't make C programs larger. They make the source code larger. That makes it harder to read.
  - kazinator 9y ago
    I can't understand your comment; can you make greater use of one-letter words?
    - shitgoose 9y ago
      z^n=x^n+y^n what can be greater than this?
      - kazinator 9y ago
        I have a marvelous response for you, but even if I use nothing but one-letter words, it doesn't fit into this margin. Oops, I see we are devolving into Reddit. Alas, at least the end is near; recursion bottoms out at 4chan which is just one stack frame down.
modeless 9y ago
> You think if I need to write C, that I should do things that make my program larger and slower and less correct? Yes (marginally), when those things are at odds with the tools and conventions of C, because there are serious downsides you don't list. Compiler error messages will be difficult to understand. Tools for code analysis and debugging will be less useful or even completely unusable. Most importantly, because your personal style is alien to other people you lose the ability to collaborate with other developers. A language designed for this would mitigate most of those downsides.
- geocar 9y ago
  > Tools for code analysis and debugging will be less useful or even completely unusable. If you don’t put bugs in the first place this causes very little problem in practice. > because your personal style is alien to other people you lose the ability to collaborate with other developers. Another solution is to expand the program by adding white space and long identifiers after it is written. This works better for me since if someone wants to change my program it’s because they want it to do something that I didn’t.

by geocar 9y ago

kazinator 9y ago

Longer identifiers don't make C programs larger. (Well, shared libraries have larger symbol tables, and unstripped executables have bigger debug info.) Using multiple lines and indentation doesn't change executable code.

geocar 9y ago
> Longer identifiers don't make C programs larger. They make the source code larger. That makes it harder to read.
- kazinator 9y ago
  I can't understand your comment; can you make greater use of one-letter words?
  - shitgoose 9y ago
    z^n=x^n+y^n what can be greater than this?
    - kazinator 9y ago
      I have a marvelous response for you, but even if I use nothing but one-letter words, it doesn't fit into this margin. Oops, I see we are devolving into Reddit. Alas, at least the end is near; recursion bottoms out at 4chan which is just one stack frame down.

modeless 9y ago

> You think if I need to write C, that I should do things that make my program larger and slower and less correct? Yes (marginally), when those things are at odds with the tools and conventions of C, because there are serious downsides you don't list. Compiler error messages will be difficult to understand. Tools for code analysis and debugging will be less useful or even completely unusable. Most importantly, because your personal style is alien to other people you lose the ability to collaborate with other developers. A language designed for this would mitigate most of those downsides.

geocar 9y ago
> Tools for code analysis and debugging will be less useful or even completely unusable. If you don’t put bugs in the first place this causes very little problem in practice. > because your personal style is alien to other people you lose the ability to collaborate with other developers. Another solution is to expand the program by adding white space and long identifiers after it is written. This works better for me since if someone wants to change my program it’s because they want it to do something that I didn’t.