🚀 go-pugleaf

>>>>> "Erkki" == Erkki Ruohtula <eru@tnso04.tele.nokia.fi> writes:

    >> In other words, the goal is to increases the readability of
    >> source code. This is very important when the code was written
    >> by somebody else than youself, and you are trying to understand
    >> what the h*ll the code is supposed to do. The fact that the
    >> code compiles without a single

    Erkki> I fully support this goal, but hacking GCC to support it is
    Erkki> futile (and in any case, I hate the idea of putting
    Erkki> features to GCC that are not directly part of the job of
    Erkki> efficiently and safely compiling programs, FSF should not
    Erkki> turn GCC into a Swiss Army Knife; they already have Emacs
    Erkki> :-).  

Now _there's_ a good idea!  GCC should be a compiler, and nothing
else.  If you want an enforced naming convention (which I don't), it
can be put into an Emacs mode, since it is in the stage of _writing_
the code that the convention would be used, not in _compiling_.

Then we can all decide not to use it :)

Anyway, meaningful names are always useful, and I much prefer having a
name which tells me "Main window title" than "Main window title which
is a `char *'".  If the representation of the window title were later
changed to be of a type String, then the variable name would have to
be changed to match!  Seems a bit (a) redundant and (b) error-prone to
me ...

-- Neil
--
    Help sufferers of     |  _ __        _          | As for Paul, he married  
   keraunothnetphobia.    | ' )  )      //     /    |  someone else's fiancee  
Write to your MP & demand |  /  / _  o // _   /_  o |     and quickly lost     
 an end to space debris.  | /  (_</_<_</_/_)_/ <_<_ |        his hair.