END keyword not uppercase.

[segfault]

This seems to be a bug, albeit a minor one. When selecting Tools/Options/Words/UPPERCASE the keywords are supposed to be uppercase when code is inserted, but "end" in procedures isn't. e.g. what you actually get is this :

Code: Pascal  [Select][+][-]

1. PROCEDURE TForm1.Button1Click(Sender: TObject);
2. BEGIN
3.  
4. end;    

I'm using Lazarus 2.0 on Win32.

[Thaddy]

IT SHOULD BE ALL LOWERCASE. Uppercase was alright when Pascal got invented....We only had uppercase...
Give the eyes some rest, please, and don't ask for dinosaurs to be raised from the grave.
If there's an option for that, KILL IT. 
To some extend I would allow propercase: your own declarations, classes, records, objects and members of those.

[segfault]

IT SHOULD BE ALL LOWERCASE

Is this the official line or the world as it should be according to Thaddy? 

I guess it's a matter of preference. I know keywords are bold but I don't see how uppercase makes MORE work for the eyes. Didn't you just use capitals in your reply for emphasis? 

[wildfire]

Is this the official line or the world as it should be according to Thaddy? 

It's generally accepted but as you know Pascal is case independent. If you're the only one reading your code then it's down to your preference.

I'm with Thaddy though, it's easier on the eyes if keywords are lower case.

[Thaddy]

It is a matter of preference. Feel free to use it - in private -....
I don't like the view and I don't like a finger occupied uselessly while typing.
But indeed it is a matter of opinion, although most people use lowercase.
(Although I acknowledge that if the option is offered, it's a bug...)

[Handoko]

I vote for lower case too.
Although I was a BASIC lover.
(BASIC use uppercase)

[wp]

Whatever the taste, it is a bug and should be reported in bug tracker.

[ASerge]

Is this the official line or the world as it should be according to Thaddy? 

http://wiki.freepascal.org/Coding_style:
...See the Lazarus coding guidelines: DesignGuidelines:
...Since one style is easier to read, Lazarus follows the CodeGear Coding Style Guide lines:
...
3.6 Reserved Words
Reserved words and directives should be all lowercase. This can be a bit confusing at times. For instance types such as Integer are just identifiers, and appear with a first cap. Strings, however, are declared with the reserved word string, which should be all lowercase.

[Thaddy]

Yes, but it is still a bug when such an option is offered and the end part end up as end. instead of END... This is the case, as wp and I noted.

[440bx]

The whole lowercase and uppercase thing is a bit strange.  The majority of COBOL programs are all written in uppercase and, COBOL in lowercase looks strange. 

I remember using a computer that used BASIC and if you typed something in lowercase, it would automatically uppercase it.   That pretty much settled the issue there... chuckle.

Pascal code doesn't look right in uppercase. 

Ultimately, except with case sensitive languages, it seems to be mostly subjective.

[BeniBela]

I think we should all be more adventurous and use something more varied:

Code: Pascal  [Select][+][-]

1. pRoCeDuRe TFoRm1.BuTToN1cLiCk(SeNdEr: ToBjEcT);
2. BeGiN
3.  
4. EnD;    

[Peter H]

Look here:
https://books.google.de/books/about/Algorithmen_und_Datenstrukturen.html?id=kKMDBgAAQBAJ&printsec=frontcover&source=kp_read_button&redir_esc=y#v=onepage&q&f=false
I personally, in the time of color pretty printing, prefer lowercase for keywords.

BTW, at page 38, there is the proof, Niklaus Wirth used "äöü..." in variable names. Can FPC do this?

[Ñuño_Martínez]

It is a personal taste thing, but I'm with mr. segfault here:  I find keywords uppercase and identifiers calmel-case (except constants) easier to read even with syntax highlighting.  May be because I'm used to it (I started with BASIC then QuickBASIC).

[ASerge]

Of course, everyone likes its style, but when we publish code, uploaded on forum, need to adhere to common style. It's like social behavior: even if you're like to being naked at home, it's better not to do it on the street.
Moreover, when I see such code in FPC sources:

Code: Pascal  [Select][+][-]

1. Procedure getdir(drivenr:byte;Var dir:shortstring);

I immediately get the feeling that the code was written by amateurs.
But if it is in the form:

Code: Pascal  [Select][+][-]

1. procedure GetDir(DriveNumber: Byte; var Dir: ShortString);

this means that the author has published the code, knows how to work in a team and is probably more professional.

[munair]

The days that BASIC used or converted keywords to uppercase also belongs to the dinosaurs. These days VisualBasic uses propercase aka titlecase by default. Personally I would vote for lowercase keywords and case dependency at the same time.