PureBasic Forums - English

Hi, everybody!

In the german forums we've just found out, that ForEver is wrong because Forever is one word. It could misslead to a for-loop when a newbie is reading it. Maybe we should change this.

Here is the original topic:
http://www.purebasic.fr/german/viewtopi ... 843#234843

Or maybe the PureBasic Team could tell us why they've chosen "ForEver".

Regards,
Daniel

i prefer EVER for forever ForEVER, coz this looks Ever nicer For Forever and is IMHO more readable.

forever ForEver !!!

i prefer Do...............Loop !! for the infinite loop

for Repeat in principe is only Repeat........ until

dobro wrote:i prefer Do...............Loop !!

This is no option. We will keep the word "Forever" . We just discuss about the u/lcase of each letter.

Yes you are right with Until, but some people like to use Break instead of Until.

Nah, let's stay in pure PureBasic style (mind the caps ) and change the syntax a little. (Actually, I like Do..Loop best )

change only for all pb word, so is

ts-soft wrote:change only for all pb word, so

Code: Select all

EndEnumeration

is

Code: Select all

Endenumeration

No, Forever is one word, End Enumeration are 2 words.

the word stems are for and ever!

PureBasic is case insensitive, right?

DarkDragon wrote:

dobro wrote:i prefer Do...............Loop !!

This is no option. We will keep the word "Forever" . We just discuss about the u/lcase of each letter.

Yes you are right with Until, but some people like to use Break instead of Until.

Maybe Do ... Loop is no option, but it would be cool (less chars to hack and no Up-/Lowcase discussions )

But I would see also other additions, a simple Exit If a>b seems to be easier than If a>b : BreaK : Endif

Michael

Michael Vogel wrote:... a simple Exit If a>b seems to be easier than If a>b : BreaK : Endif

according to PureBasic convention, it should be written ExitIf...

Michael Vogel wrote:But I would see also other additions, a simple Exit If a>b seems to be easier than If a>b : BreaK : Endif

BreakIf would be more consistent, but then we'd need ContinueIf as well, and things would get messy... I think what we need is a universal one-line if-construct, so I'll re-propose my idea for it: let's have Test, True and False -keywords, so that we can have nice one-line constructs like this:

Test Variable=1 True Variable-1 False Variable=1
Test ResultFromSomeProcedure() False ResultWasTrue=#False
Test BreakFlag True Break

The same with If/Else/EndIfs would take quite a few lines more... (Or you could use colons, but then it wouldn't be so sexy!)

*Edit* Maybe I'll just post it in feature requests...

The correct English word is "Forever" with a lowercase E.
It's currently wrong but it's never bothered me so far.

> The correct English word is "Forever" with a lowercase E.
yes, but the camel case word is ForEver

Camel case only applies to different words in the phrase, not words themselves.