pseudotypes

[Psychophanta]

There are three types of pseudotypes:

p-ascii - to force the parameter to 8 bit Ascii
p-unicode - to force the parameter to 16 bit Unicode (DWCS)
p-bstr - to force the parameter to BSTR format (Visual Basic)

Couldn't be:
p_ascii
p_unicode
p_bstr
or simply: ascii, unicode and bstr

The minus "-" sign confuses a lot.

[blueznl]

spycho got a good point there, underscores may make more sense...

[Berikco]

Yes, i must agree the minus sign is a bad choice...

[Psychophanta]

Uffhh! at least i got an 'agree' for one thing
Even perhaps it was done like that to avoid to be confused with any eventual user defined Structure with the same name. But in that case there are another signs like ':' or wrap it into {} or something like that in order to difference it clearly...

[Fred]

no, as p_ascii can be a regular type. p-ascii is a special type, there is no confusion/collision possible with regular strutcure/interface types. BTW, why don't you try to use the new features instead of trying to change something we had spend of lot of time to think of ?

[Psychophanta]

BTW, why don't you try to use the new features instead of trying to change something we had spend of lot of time to think of ?

You're right!
I hope to not find lots of bugs after converting codes...

[Fred]

If you find some, please report them so we can fix them quickly and have a nice final release.

[Shannara]

So with the BSTR format, we can have something like the following:

Code: Select all

ProcedureDLL.b-str HelloWorld()
   ProcedureReturn "Whee"
EndProcedure

Then in theory, in Vb, after declaring the DLL command, we can call it..

Code: Select all

dim I as string
I = HelloWorld()

Call MsgBox("Test", I)

So no need for that work around stuff that was posted awhile back, for using PB dlls in VB?

[Shannara]

Nvm, workaround is still required.