RE: Removing the last optional parameter from an existing exportprocedure

Changing from "const" to "value" shouldn't cause any problems in the caller

Oh yes it should.

In the const case you're passing a 16 byte pointer.

In the value case, you're passing a however many byte variable value.

On the other hand, removing const shouldn't cause the caller a problem, as the 
caller is still passing
a pointer.  At least until the caller is recompiled.  The if the caller was 
relying on the compiler to
convert from a literal or something the caller won't compile anymore.

HTH,
Charles




This e-mail transmission contains information that is intended to be 
confidential and privileged.  If you receive this e-mail and you are not a 
named addressee you are hereby notified that you are not authorized to read, 
print, retain, copy or disseminate this communication without the consent of 
the sender and that doing so is prohibited and may be unlawful.  Please reply 
to the message immediately by informing the sender that the message was 
misdirected.  After replying, please delete and otherwise erase it and any 
attachments from your computer system.  Your assistance in correcting this 
error is appreciated.