Re: Interresting difference in Normal-Returns/Expression-Functions and Extended-Returns.

[Stephen Leake <stephen_leake@stephe-leake.org>]

Shark8 <onewingedshark@gmail.com> writes:

> Here's some output:

From what compiler version, on what OS, on what CPU?

>> 4. Keywords to be written all lower case, if you want others be able to
>> read your code.
>
> ... and here I thought we had these nifty tools for formatting
> source-code according to the user's preference. 

Way off base. This is a volunteer group, and there _is_ a common style
of lowercase for reserved words.

Yes, a pretty printer could rewrite your code, but that's an extra step;
every impediment between me and understanding your code makes it a
little less likely I will bother.

You could just as easily take that step, and save everyone else the
effort. Consider that part of the cost of deciding to not follow the
common style.
 
Being polite to the people you are asking to help you is only common
sense.

> It is not my fault
> these aren't well-integrated into your IDE/text-editor. 

Emacs Ada mode does not support that particular rewrite; no one has
asked for it! I'd have to use gnatpp on the command line. Which I've
_never_ had to resort to before for code posted in this newsgroup.

On the other hand, since Emacs Ada mode is an open source all-volunteer
effort, it _is_ your fault for not contributing support for gnatpp to
it, since you seem to feel it is important!

>-- IOW, if
> casing mattered I'd expect it to be enforced by the language.

There is a big difference between language rules and style rules; it's
time to learn that. Ada is case-insensitive for well established
software engineering reasons, and styles exist for equally well
established reasons. They are both required for successful projects;
they work together.

-- 
-- Stephe