END keyword not uppercase.

[VTwin]

I programed in FORTRAN before it was Fortran.

Sounds like a bug, but I generally agree with Thaddy. I use lower case for key words, basic data types (byte, integer, string, double), and parameters (or, horrors, camelCase).

[bylaardt]

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

1.   insignificantvarname  // for loops or other situations when i can reuse it.
2.   ThisVarHasAContext    //  when i must explain
3.   DO_NOT_DARE           // it's a screaming code
4.   BDWTHISCANBESOCONFUSE // no comments
5.  

lower or upper? i don't care... i merely can do it!

[VTwin]

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

1.   insignificantvarname  // for loops or other situations when i can reuse it.
2.   ThisVarHasAContext    //  when i must explain
3.   DO_NOT_DARE           // it's a screaming code
4.   BDWTHISCANBESOCONFUSE // no comments
5.  

lower or upper? i don't care... i merely can do it!

IMHO, consistency, readability, and not yelling is helpful. At my age I try to write self-documenting code that can be passed along.

[bylaardt]

IMHO, consistency, readability, and not yelling is helpful. At my age I try to write self-documenting code that can be passed along.

+1

[440bx]

lower or upper? i don't care... i merely can do it!

People can jump off the top of a high-rise without a parachute, it doesn't imply it's a good idea.  That said, TTBOMK, there have not been any casualties as a result of someone jumping off an uppercased letter (with or without a parachute.)

[Thaddy]

Well, I have this idea to have a poll to make C keywords mandatory uppercase in C21 (Plz vote YES, we don't care, cuz Pascal is case agnostic).
We can keep it under the radar of the C community and publish a draft RFC after the outcome, thus setting a precedent..
(It's  not that strange: it is like how C++ was born)

[Bernd82]

Is this bug already repaired? I face the same problem. I personally like all keywords uppercase.

[marcov]

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

http://wiki.freepascal.org/Coding_style:

That is writable for everybody, so it is hard to consider something like that "official".

[Bernd82]

Thanks for your effort. Unfortunately I do not understand your answer.

Is the problem solved or can I solve it myself?

P.S. The problem only happens when automatically generating a method for an event. The normal BEGIN ... END works.

[Martin_fr]

Tools > Options:
Codetools > Words

Keyword policy: Uppercase

seems to work in 2.1

[winni]

Hi!

As long as the fpc/Lazarus sources have no clear idea about upper/lower/mixed
I don't care:

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

1. MAXWORD

but

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

1. maxSmallint  

I don't wanna hear some explanations like "historical reasons" or "C" or ....

The whole discussions is nonsense.

Winni

[Bernd82]

Thank you Martin_fr, I will update from v2.0.8 to 2.1. Let's see if it works. Thanks again for the hint!

I already thought that this might be an almost religious theme  ;-)

[Martin_fr]

Just checked, the same setting/option exists in 2.0.x.

But I have not tested it there (I do not use it myself). I tested a single "end." (inserted when I hit enter) in 2.1 and that was uppercase.

That is for "end" auto-inserted, when you press return.

if you want to have any "end" that you type (by hitting the 3 keys e,n,d) to be converted, you may be able to do that with code-templates.

As for Jedi.... , I have no idea / not looked into it.

[Bernd82]

I know, that the option uppercare exists and I have accordingly set it to uppercase for keywords.

The problem only occurs, if I generate let's say an OnClick method for a button by double clicking the button. Then the following code is generated with a lowercase end:

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

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

It doesn't happen if I type BEGIN and type key [Return]. In that case everything is correct:

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

1. FOR i:=1 TO 10 DO BEGIN
2.   |
3. END;

[Martin_fr]

ok, that lower case "end", with all else correctly uppercase, that would be a bug.

Still wrong in 2.1

Check if there is a report on the bugtracker, and if not create one.