So... have you added a bugtracker entry to give that information to the developers so the patch can be implemented?
Hum, no, because Michal Wallace old patch was not accepted (I dont want to impose something, even if it is better
)
A patch should be tested against the following cases:
- fpc using fpc dll using normal linking
- C using fpc dll
- the above cases using dynload.
Indeed, not yet tested with normal linking (no use of dynlib), nor tested by a fpc application using fpc library.
What tested and works perfectly :
Java using fpc libraries ( with Java-dynload).
Python using fpc librares (witjh Pythn-dynload).
Thanks.
[EDIT]
In all cases, printing out paramstr and paramcount() and environment variables from inside the library should be verified to work.
Yep, it seems they are some problems with paramstr and paramcount(), i will do more test to see what is wrong...