At 10:52 AM -0700 7/24/03, Mark Berryman wrote: > why not simply have the utility that >turns the .XS file into a .C file surround the routine/function names >with the appropriate #pragma statements to make them compile as_is but >leave everything else untouched. This should handle whatever names the >extension author may choose to use without impacting the ability to link >to anything else on VMS. > >Is there any reason why this wouldn't work?
xsubpp already shortens long symbol names, so there's no theoretical reason it couldn't take other actions to clean up symbols as well. One reason it doesn't may be that those pragma statements you're talking about weren't yet available when the current XS processing was developed and debugged. Even now we'd have to consider whether compilers that are too old to support the as_is pragma are also too old to consider worth supporting for other reasons. I haven't looked at the code to see how tricky it would be to remember all the symbol names and pick out which ones are identical except for case (I guess you could just apply the pragma to *all* the symbols). There are risks with putting too much VMS-specific code in xsubpp, mainly that folks who make changes without having the ability to test on VMS might break something without knowing it. But a working patch would certainly get consideration. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
