[DONE] 1.877 / 4.30b4: String Problem

[Vladi]

Is this a known bug? What is the status?

Lib:

Code: Select all

ProcedureDLL$ proc(a)
   ProcedureReturn Str(a)
EndProcedure

ProcedureDLL$ p(b)
   ProcedureReturn proc(b)
EndProcedure

Pgm:

Code: Select all

Debug proc(3)

Debug p(2)

Second statement crashes.

[gnozal]

It's a known limitation with PB versions >= 4.20.

Don't call exported string functions in your library, because of the 'RET X+4' fix : see http://www.purebasic.fr/english/viewtop ... e&start=22

Just add a 'dummy' function through which the exported string function operates.

[Vladi]

Thanx for your prompt answer. But what do you mean with a dummy function? I think any other function in between (inside the lib) will crash as well?

And the "limitation" will stay? Don't you think it will make user libs unusable for anything other than elementary functions?

[gnozal]

Thanx for your prompt answer. But what do you mean with a dummy function? I think any other function in between (inside the lib) will crash as well?

You could do it like this :

Code: Select all

; proc
Procedure$ proc_private(a) ; private
  ProcedureReturn Str(a) 
EndProcedure 
ProcedureDLL$ proc(a) ; exported
  ProcedureReturn proc_private(a) 
EndProcedure 
;
ProcedureDLL$ p(b) 
  ProcedureReturn proc_private(b) ; use private version in your library
EndProcedure

Code: Select all

Debug proc(2)
Debug p(2)

Don't you think it will make user libs unusable for anything other than elementary functions?

No, you only have to use a 'dummy' function if you call an exported string function inside your library.
No problems with non string functions, private string functions or with exported string functions not called from inside the library.

[Vladi]

Ok, that's not nice, but it works, thanks.
But I think you should mention something about this in the manual...

[ABBKlaus]

Thanks Vladi.
The help file is updated. You can read it online : http://www.tailbite.com/help/index.html