Another Reason for IntPtr Type

[Louis]

Hi Erel, Another reason we'll appreciate passing and receiving C Pointers, which is IntPtr in .NET is because most C libraries require you to pass a pointer or structure by value, and some even return structures and/or pointers to retrieve and store objects into unsafe memory. Lots of Speech and sound API'S for both the desktop and device use these heavily. Let me know what you think, or I'll see what's up in the next version of B4PPC!

[Erel]

IntPtr conversation will probably be supported in the next version.
Note that it is possible to create an IntPtrEx object which will wrap a pointer.

[agraham]

Originally Posted by Erel

Note that it is possible to create an IntPtrEx object which will wrap a pointer.

Please could you give more detail on this Erel as I can't locate anything about it.

[Erel]

There is no such thing. What I've meant is that if you need to use pointers (IntPtr) you could create a library which will include an object that holds pointers.
Similar to the ControlRef property of controls.

[dzt]

There is an easy way to convert IntPtr to Integer (manageable by B4PPC) and vice versa. See my dzHW source (latest version) posted here Useful Library