PureBasic Forums - English

Restored from previous forum. Originally posted by Danilo.

Hello !!

I think the command "FrontColour"
should be "FrontColor".

I know that "Colour" is right,
but "Color" is the word that is
used *everywhere* in the world.

"Color" is the standard, so it
would be better to rename the
command to "FrontColor".

Thanks,
...Danilo

(registered PureBasic user)

Restored from previous forum. Originally posted by fred.

Ok, I will change that.

Fred - AlphaSND

Restored from previous forum. Originally posted by MrVainSCL.

Normaly I would say that you are right, but I think it is to late to began renaming the commands. I dont want to change all my sourcecodes with any new PB release!

Maybe there are some commands that could be changed but its just to late!

Anyway, if you realy need these keywords, why not creating a procedure with your own keywords?! Only one possibillitie....


PIII450, 256MB Ram, 6GB HD, RivaTNT, DirectX8.1, SB AWE64, Win98SE + Updates...

greetz
MrVainSCL! aka Thorsten

Restored from previous forum. Originally posted by tranquil.

Mayor Changes in 2.90:

Renamed FrontColour to FrontColor
Renamed PannelGadget to AddPannelGadget
Renamed End to .....

.....

Just kidding but a little bit ironic.

Mike

Tranquilizer/ Secretly!
Registred PureBasic User

Restored from previous forum. Originally posted by Danilo.

A little Search&Replace will do it.

I dont want to rename many commands,
but "FrontColour" is a very bad
name for "FrontColor".

Everybody is using "Color" every time,
so i think this *1* command should be
renamed.

The thing with the Procedure isnt the
right way of doing it, if the name
is really ugly.
I would do it if i only want my own
style, but the thing with FrontColour
is a gerneral style question.

It doesnt call "FrontColor" directly,
but calls a procedure "FrontColor"
that again calls "FrontColour".
Thats VisualBasic...


Fred can also make a "FrontColor"
and let the "FrontColour" in the
Library too (for compatibility),
but it is his own choice.


cya,
...Danilo

(registered PureBasic user)

Restored from previous forum. Originally posted by fred.

Mayor Changes in 2.90:

Renamed FrontColour to FrontColor
Renamed PannelGadget to AddPannelGadget
Renamed End to .....

I've ever done that for any release ? . If a command is badly named, it must be changed. PureBasic is young enough to do that. How many time did you use FrontColour() in your progs ? I guess 2-3, not more. It's easy to change and make the whole basic better.

Fred - AlphaSND

Restored from previous forum. Originally posted by Fangbeast.

A major Grr to you guys. I always spell Colour as it's the proper spelling!! COLOR is the AMERICAN way of doing things, not the VB way. VB is BASICally (LOL) American so it inherited the spelling.

I don't want to see PureBasic Americanised just because one of you doesn't like the spelling. I shudder at the thought!!

Can anyone here me shuddering over here???? (Major ROFL)

Fangles

Restored from previous forum. Originally posted by El_Choni.

Hi,

In every programming or scripting, even in html, I've always seen colour commands spelled as 'color', so I think PureBasic should follow that rule in order not to confuse new users and allow easy changing between languages (some of us use different programming tools along the day). You may think that, as I am spanish, I don't care about correct English spelling. But if, as you say, 'color' is the american way of saying 'colour', I don't think american PureBasic users will see it as incorrect spelling. Personally, I wpould like every PureBasic command in Spanish, but I don't think that is going to happen. By the way, Fred, what about macro support? That would allow using the names you want as valid PureBasic commands and, as the macro source would be included with the code, it would be 'portable'. I know Procedures allow this, but with macros you would save a call.

That's all, have a nice day,

El_Choni

Restored from previous forum. Originally posted by Danilo.

Yeah !!

I was also thinking about MACROs,
but i didnt ask because i thought
i´m the only one who wants MACROs.

cya,
...Danilo

(registered PureBasic user)

Restored from previous forum. Originally posted by Fangbeast.

Hi,
In every programming or scripting, even in html, I've always seen colour commands spelled as 'color',

But if, as you say, 'color' is the american way of saying 'colour', I don't think american PureBasic users will see it as incorrect spelling. Personally,

I way having a joke with all of you!! (ROFL = ROLL ON FLOOR LAUGHING) I am a purist with languages but I don't tend to take it very seriously and when I say COLOUR is English and COLOR is American, I should probably point out that COLOUR is oringinally from French and the English adapted it!!!

Since I speak English, American, Australian, Hungarian and a little Italian, i'm used to speaking a mixture of languages.

One good idea (probably way way down the track) is to allow PureBasic to load and use a language file of the country's choice. After all, if my memory serves me correctly, Most BASIC languages use all Keywords, Sub names etc in tokenised form after compilation so using another language for keywords should not really be a problem.

But, I could be wrong, Ony Fred would know with his compiler.

Have a nice day.

Fangles

Restored from previous forum. Originally posted by Franco.

Ciao Fangles come stai? Tutto a posto?
Spero che ti va bene. Ci vediamo.



Have a nice day...
Franco

Restored from previous forum. Originally posted by PB.

I know that "Colour" is right, but "Color" is the word that is
used *everywhere* in the world.

Really? It's not spelt that way in the UK or Australia.
What makes America so special (no offence intended)? Why not
just make a procedure to rename it if you don't like it?

Fred: I asked this before and I don't know if it's possible, but
is there a way you can somehow make a "keywords" file so that people
can change the PureBasic keywords for themselves? You know,
a text file like so:

FrontColour=FrontColor

So that people can do what they like without disturbing others.


PB - Registered PureBasic Coder

Edited by - PB on 08 January 2002 21:48:21

Restored from previous forum. Originally posted by PB.

[Procedures don't] call "FrontColor" directly, but calls a
procedure "FrontColor" that again calls "FrontColour".

But the end result is the same. For example, the follow two pieces of code
both compile to exactly the same size executable, so what's the problem?

Example 1:
m$="test" : MessageRequester("title",m$,0)

Example 2:
Procedure MsgBox(m$)
MessageRequester("title",m$,0)
EndProcedure
MsgBox("test")


PB - Registered PureBasic Coder

Restored from previous forum. Originally posted by fred.

The problem is Windows which does executables with 512 bytes size increment each time.. So if you add less than 512, you will see nothing.

Fred - AlphaSND

Restored from previous forum. Originally posted by PB.

The problem is Windows which does executables with 512 bytes size increment each time.. So if you add less than 512, you will see nothing.

Ah crap, really? Damn. Thanks for the tip!


PB - Registered PureBasic Coder