| Charles Bailey wrote:
|
| > This probably is true of pm_apiversion, but we constrain xs_apiversion by
| > the GSMATCH restrictions under VMS. (I hope we'll eliminate this for 5.6.1,
| > at which time xs_apiversion can be relaxed considerably.)
|
| OK. Am I interpreting your comment correctly: "I hope we'll eliminate GSMATCH
| restrictions by 5.6.1"? Or something else? Thanks.
Ayup. What I'd like: code that scans an existing shareable image to find
its major and minor IDs and symbol vector, and then compares it to a vector
handed to it, creating a linker options file that's compatible if at all
possible (new names at the end, etc.) with appropriate GSMATCH. What I'd
settle for in the interim: code that parses an existing perlshr_bld.opt
to figure out the current state and then uses a vector handed to it to
construct a linker options file, etc.
Regards,
Charles Bailey [EMAIL PROTECTED]
