Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Is there another way? I'm just looking to save a step if possible. For example, what would be nice is if I could BinaryAlloc and tell it where the data is. That would save me the copying step.
Note: I am aware of and have used IC(32) - that works, but only for 1,2 or 4 byte values.
IntControl(32) set to peek 1 byte at a time in a loop looking for a terminating NULL byte would effectively perform the same thing as the CRTL string copy functions. The key thing is to test for the NULL byte that terminates the string. Of course, a native string copy function that does all of that and returns a WIL string variable would be more efficient than iterative calls to IntControl(32).
Article ID: W16461
File Created: 2005:02:18:12:20:50
Last Updated: 2005:02:18:12:20:50