> Can there be preprocessor directives
> in it e.g. #define to define return codes?
No basically.
They can be there (the parser won't choke on them since... version 6 I think?) but they won't be processed.
-SHAWN-
> in it e.g. #define to define return codes?
No basically.
They can be there (the parser won't choke on them since... version 6 I think?) but they won't be processed.
-SHAWN-
Last one was too quick!!!..
A question on header file contents that VEE supports. Can there be preprocessor directives in it e.g. #define to define return codes?
Simon
--
_____
This e-mail (including any attachments) is intended only for the recipient(s) named above. It may contain confidential or privileged information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please contact the sender by telephone (+44-1454-284800) and destroy the original message. Any statement and/or opinion not related to this company's business and expressed in this message is that of the author and does not necessarily reflect those of Icera. This company does not take any responsibility for the views of the author in any matter not related to the company's objective.
_____
---
You are currently subscribed to vrf as: hua_jing@agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".