Hello Yvan,
It is only one memory location because it is just a typecast, no
converstion is done.
Can you tell also what access violation it exacly is ?
Are you calling sendStr from same thread context as the one where
TWSocket is created ?
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/en
Hello,
We have a problem with an application that have 2 threads, when we try to
send 2 different messages by 2 thread using 2 instances of twSocket V5.25.
Each thread got their own socket connection. If the threads are sending at
the same time the application crash with an access violation
