[Implemented] Compiler features

[Polo]

Hi,
I've some request for the compiler :
One, not really important, but just wondering : why, in pb, we use the name of "procedure" instead of "function" like in the other basics ? Not important, but i just wanted to know
The other one, much more important, bu Fred already know it i think : I would like to get the possibility to add optionals parameters in a procedure, like in Blitz, and if possible to put it compatible with Tailbite

Code: Select all

Procedure MyFunction (param1,param2,optionalparam=0)
Endprocedure

[Blade]

Because functions and procedures are the same thing. The only difference is that the former returns a value.
So if you need a procedure, just write a function and do not return a value, or vice-versa
IMHO

[Polo]

Yeah, I know they are the same things, that's why i'm wondering why not having them called Function But i don't really care, i just wanted to know

[DarkDragon]

Because some people say proc instead of func and so Windowfunc became Windowproc.

[blueznl]

because gfabasic called them procedures?

[johndehope3]

What I don't understand is why we have to call them anything at all? Instead of this...

Code: Select all

Procedure.s MyName() ... EndProcedure

What's wrong with this...

Code: Select all

MyName.s() ... EndProcedure

While I'm on the topic, how about just End instead of EndProcedure, EndIf, etc.
Also, why not Return instead of ProcedureReturn?
I think this would go a long way towards making PureBasic easier to code in.

[GedB]

johndehope3,

I rather like the use of the different End syntaxes. It makes intention much easier.

Ruby just uses plain end and this can cause problems with matching ends if my whitespace ever goes out of line. This is a particular problem if code is being copied.

If the extra typing is bothering you just switch to japbe and let autocompletion take care of it.

[Polo]

Anyway i hope fred plans to work on the optional parameter thing, because it would be a lot useful !!

[freedimension]

What's wrong with this...

Code: Select all

MyName.s() ... EndProcedure

Answer:

Code: Select all

Proc1()
;Do weird things here
Proc2()
;Do even more weird things
EndProcedure

Now, what is the Procedure and what is just a procedure call?

[wcardoso]

Well I think EndProcedure, EndIf, etc. is better than simply End because when the source file becomes bigger you can undestand more clearly the body of loops, procedures, etc. Specially if there are deep nesting

[Psychophanta]

What's wrong with this...

Code: Select all

MyName.s() ... EndProcedure

Answer:

Code: Select all

Proc1()
;Do weird things here
Proc2()
;Do even more weird things
EndProcedure

Now, what is the Procedure and what is just a procedure call?

What about EndProcedure Proc1()
BTW, i guess Fred preferred "Procedure" instead "Function" because he is a native french speaker

[nco2k]

Code: Select all

Procedure Name()
  ;
EndProcedure

is good, the way it is... :roll:

c ya,
nco2k

[Polo]

>Psycho : I'm also native french speaker, and in french, instead of function we would say "fonction", but procedure ?? I don't like this word
But i don't care

[Psychophanta]

Are you sure "Procedure" come not from french ??
"Bureau" is a word used in english, but it comes from french too.
Well, anyway then "Procedure" sure comes from Pascal computer language, don't?

[thefool]

but anyway, a procedure RETURNS something, and a function DOES NOT!!!

so, if we change it, it would become OUT of standard, and we would have to change our source too! [not the hardest change, though]

thats the difference and it is in most other basics too!