It seems I can't explain my point: 90% of WinAPI functions need a pointer to a NULL terminated sequence of bytes to pass some text. VB needs to convert that each time it calls the OS, not only in ANSI (and that's silly since most WinAPI calls accept unicode strings now) but also it must retrieve the pointer before (that's ONE of the reasons why it's sooo slow). I personally see no reason why a string should be longer than 64KB (if you need that, it means you're using a string for an aim a string wasn't created for, IMHO).
What I'd like instead it's the UNICODE support for strings. So a BSTR Unicode string (together with current string type) would be very nice for PB.
Ever seen in VB using Byval As String in a declare?
It does at least one thing, it passes the pointer to the BSTR data compatible with any api call.
I said that even BSTR contains a 0 char but 1byte outside it's length range.
We should not discuss the uncicode to ansi conversion matter in VB, it has not much to do with this request.
If the unicode is converted + you are using Byval Text$ it will pass a pointer to the ANSI memory.
If it's BSTR or GlobalAlloc() whatever.
I will no longer debate this, because i mentioned some additional features and are prob. disregarded.
So no use to continue i guess.
I'll add just a tiny note: what about if you need a pointer to a string to work with, without copying it? For example an extern function in C like this -> GetString(char *string).
ByRef doesn't pass a pointer in a way C can work with it. This is a real problem you get in real life-work with VB.
Seldon wrote:ByRef doesn't pass a pointer in a way C can work with it. This is a real problem you get in real life-work with VB.
Fortunately, It's not a problem with any real life work vb programmers I know, aka state db & normal application programmers. Not to mention the guys who created the first version of the unreal editor in VB
But then again.. I guess it depends on what kind of "real life" work your talking about?
