[Implemented] A few VB touches....

[Yogi Yang]

Like in Vb there should be provision for forcing a developer to first declare variables and then use them if the developer wishes. I would go for a parameter like - Option Explicit (as implemented in VB) so if developer needs to force himself to declare each and every variables he will put Option Explicit at the top of the code module.

There should be provision for passing parameters to a function/routine either - ByVal or ByRef this would really help esp. ByRef as in VB.

A large set for Functions for manuplating Strings like those in VB and more, Arrays & such collections features as implemented in VB.NET would be great to have in PB.

I know there are many workarounds in form of UserLibs but it would be nice to have these features built right in PB ranther than in third party UserLib. Generally developers of UserLibs are hobbies and may loose their interest in a particular UserLib and many discontinue developing it or ditch it all togather. And over a period of time these UserLibs may become incompatible with newer versions of PB.

What do other developers think about this

[maw]

Like in Vb there should be provision for forcing a developer to first declare variables and then use them if the developer wishes. I would go for a parameter like - Option Explicit (as implemented in VB) so if developer needs to force himself to declare each and every variables he will put Option Explicit at the top of the code module.

In PB4 you now have EnableExplicit which does just that.

[PB]

> there should be provision for forcing a developer to first declare variables

Use the EnableExplicit command.

> A large set for Functions for manuplating Strings

Like what? There are many string commands at the moment.
Or maybe I could write a macro for... ah, forget it.

[traumatic]

Or maybe I could write a macro for... ah, forget it.

[Dare2]

[Kale]

Like in Vb there should be provision for forcing a developer to first declare variables and then use them if the developer wishes. I would go for a parameter like - Option Explicit (as implemented in VB) so if developer needs to force himself to declare each and every variables he will put Option Explicit at the top of the code module.

There should be provision for passing parameters to a function/routine either - ByVal or ByRef this would really help esp. ByRef as in VB.

A large set for Functions for manuplating Strings like those in VB and more, Arrays & such collections features as implemented in VB.NET would be great to have in PB.

I know there are many workarounds in form of UserLibs but it would be nice to have these features built right in PB ranther than in third party UserLib. Generally developers of UserLibs are hobbies and may loose their interest in a particular UserLib and many discontinue developing it or ditch it all togather. And over a period of time these UserLibs may become incompatible with newer versions of PB.

What do other developers think about this

Purebasic does not need to be like any language IMHO! and all these things are implemented in V4.0 anyway.

[traumatic]

There should be provision for passing parameters to a function/routine either - ByVal or ByRef this would really help esp. ByRef as in VB.

I second that

[Nik]

Pointers are the pure Way^^ andthis can be taken literal and philosophically

[Kale]

Pointers are the pure Way^^ andthis can be taken literal and philosophically

Agreed! Never having used VB i dont get why you would need ByVal or ByRef when you can use pointers. Am i missing something here.

[traumatic]

Am i missing something here.

Don't know.



This is not a matter of VB (other languages allow you to chose how
to pass parameters as well **), it's a matter of design/concept/needs.


Using ByVal, only a copy of the parameter will be used inside the
procedure. This prevents the procedure from changing the passed
data. Values are being preserved.

(Using a copy obviously allocates memory when calling the procedure
and comes with a certain performance hit of course.)



With ByRef (PB's way) on the other hand you're passing a memory
location, thus allowing the procedure to change the passed data,
which may not always be wanted.





** think of C for example:

Code: Select all

void ByVal(yourStruct var);
void ByRef(yourStruct& var);

[/size]

[blueznl]

pb's way is byval, not byref

[traumatic]

pb's way is byval, not byref

?

Code: Select all

Procedure AreYouSure(*var.POINT)
  *var\x = 10
EndProcedure
 
AreYouSure(myVar.POINT) 
Debug myVar\x

[Bonne_den_kule]

PB 4.00 has prototypes which can handle pointers like byref in VB.

[blueznl]

you PASS the VALUE of the POINTER

that's byval in my book (a thin book, admitted, but still)

[traumatic]

We must have different books then.