| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Are ultrix full path names excepted in the INCLUDE
for MSL's?
For the following example:
INCLUDE /usr/users/mcdonald/pseudo_built_in_types.ms;
I get the following error:
%MCCMSL-E-UNEXPCHARACTER, Unexpected character "/", in input
%MCCMSL-I-MSLLOCATION, Line: 6, File: ln.ms,
%MCCMSL-E-PARSER, syntax error: The value "/" is not expected
Thanks
Carol
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5551.1 | Include switch with mcc_msl compiler | MQOSWS::F_MONETTE | Montreal Sales Support | Mon Aug 30 1993 14:26 | 13 |
Carol, You can try to specify only the INCLUDE with no pathnames and specify it instead in the mcc_msl compiler. Ex: mcc_mcl -I/usr/users/mcdonald/pseudo_built_in_types.ms this should work Bye, Francois | |||||
| 5551.2 | yes, but... | TAEC::DOLAN | Tue Sep 07 1993 11:04 | 25 | |
...that wasn't really the question. We are working on a GDMO->MSL Translator. This program automatically generates MSL files from GDMO/ASN.1 files. One of the things we do is import "static" pieces of MSL containing, for example, the MSL TYPE equivalent of the ASN.1 CMISFilter type. Now, we allow the user of the GDMO Translator to specify where in the directory hierarchy these "static" .ms files are located. This we use to generate INCLUDE statements. A relative path name (e.g. msl/pseudo_built_in_types.ms) works just fine in an INCLUDE statement.The MSL Translator accepts that. However, as Carol points out it doesn't accept a full path name (e.g. /usr/users/mcdonald/msl/pseudo_built_in_types.ms). This is inconsistent behaviour if nothing else. If the MSL Translator is capable of accepting a relative path name then I see no good reason why it shouldn't also accept a full path name. Alternatively, you can argue that specifying a relative path name is incorrect in which case the MSL Translator ought to spit out an error for that as well. Which is it? Regards, frank | |||||