Forever ForEver...

[ricardo]

[added]Now i realise that changin the case will not break any code, however i want to keep my original comment related to changes and changes in commands, thanks
[/added]

I think that changing commands for each version is a mistake that adds unneccesary complications, so i vote for let it as it is.

*Not everyone is devoted full time to code in PB and keep commands in mind. So changing the commands each version drive to a situation in which almost any example you found in the forum wont run in the new version, unless you keep calm and take the time to figure it out what changes are needed, im sure many users quit before doing that.
I hope that this changes may stop unless is a very very critical situation with no other solution, but otherwise keep commands as it is.

My two cents.

[horst]

I do not like the keyword "forever" at all, because I have no loops that repeat forever. I have defined a constant:

#Break = 0

so I can use:

Code: Select all

Repeat
  (whatever)
Until #Break

[PB]

> I think that changing commands for each version is a mistake

Well, it's not changing the command, it's changing the auto-formatting only.
The command is still spelled the same, and means the same thing. It's just
that it would be grammatically correct in the English language, which PureBasic
uses. Currently, it's a visual error rather than spelling error, so fixing it is
very trivial and easy for the team to do, and personally I think they should
so the language looks that little bit more professional. Currently, it looks like
someone made a typo with an English word and never bothered to fix it.
That makes the program amateurish in some people's opinions, and could
be easily avoided with a simple single character correction. IMO. Anyway.

[ts-soft]

Basic is a programming language, comes from usa (Dartmouth College), so ForEver is correct

[Thalius]

heh

Code: Select all

      seLeCT eVeNTGADGeT()
        cASe 0
          iF eVeNTTYPe() = #PB_eVeNTTYPe_reTuRNKeY
            meSSAGeReQueSTeR("iNFo", "reTuRN keY PReSSeD", 0)
            seTACTIVeGADGeT(0)
          eNDIF
          
        cASe 1 ; PLAY
          dISABLeGADGeT(2,0)  ; eNABLe THe 'sToP' gADGeT
          dISABLeGADGeT(1,1)  ; dISABLe THe 'PLAY' gADGeT
      
   ; ...

s0 wTh !

on a Sidenote, this Thread is pretty amusing =P Thx !

[the.weavster]

From the urban dictionary:

1. forever

forever is until you find somthing better.
honey, i will love you forever. (six months later) honey, i'm leaving you for a 20 year old who has her clit pierced.

[IceSoft]

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.

Who is we? It is only you.

[Kaeru Gaman]

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.

Who is we? It is only you.

indeed.
... and I trashed the thread asap, but you had to come here...



> It could misslead to a for-loop when a newbie is reading it.

in the docs it's clearly connected with Repeat.
a newby who would mix up For and Repeaet would not even recognize the difference between Forever and ForEver...


time wasting bullshit... if it wasn't commercial break in CSI, I would not even be posting...

[blueznl]

Yeah, let's go back to saving world-hunger by inventing self replicating nachos... now that's Nobel-prize-worth scientific progress!

[pdwyer]

self replicating nachos

hmmmmm

maybe this thread has some merit afterall

[DarkDragon]

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.

Who is we? It is only you.

No, I did not start the thread (You should look at the facts before you write such sentences which are just insulting people through your own arrogance). mardanny71 has started it. And if you look at the dates of the postings... I started my thread here in the English bulletin board right after I posted my first opinion in the German board. I couldn't know that there are more against making PureBasic serious (No mix of AE and BE).

Please stop insulting me and leave this thread alone. It hurts me.

[dobro]

long ago I noticed that the community PurBasic
is filled with "no change"

the "no change" are numerous, and prevent some of PureBasic development in "breaking" any new ideas!

I still think that we must replace
Repeat_____forever by Do___Loop!
even if it's not here this

[PB]

Here's the final answer: http://www.youtube.com/watch?v=F7cxqX6Q3gI

[Demivec]

Yeah, let's go back to saving world-hunger by inventing self replicating nachos... now that's Nobel-prize-worth scientific progress!

Why would anyone want to "save" world hunger instead of preventing it? Even so, I put my vote behind the self-replicating nachos.


Concerning the thread topic, it was suggested that the capitalization of "ForEver" should be changed because it is one word and not two. That isn't true, it is both one word and also two words. "Forever" and "ForEver" mean the same thing. That would lead an individual to the conclusion that either choice is equally acceptable. Since a choice was already made, let that suffice.

I think the idea itself of "Repeat/ForEver" is a simple and unique way of describing a loop that has no condition for termination. If you thought about the word choice for "Do/Loop" it can be seen that it doesn't really tell you about the loop. It merely leaves out any ending condition. So out of those two choices I think a beginner would favor the "Repeat/ForEver" construct.

dobro: considering the above, maybe you would go for a "Do/ForEver" loop.

[dobro]

simply Do---Loop exists in a lot of Basic

Gfa basic (Atari)
Visual Basic
Dark Basic
quickBasic
PicBasic
FreeBasic
RealBasic
GWBasic
TurboBasic
LibertyBasic

etc .....
why invent the hot water?