At 12:32 AM -0500 2/16/05, John E. Malmberg wrote:
$ search/exact *.c "OSNAME"
****************************** D0:[CRAIG.PERL-5_8]perl.c;1
PL_osname = savepv(OSNAME);
Some how I must have missed that one. The help of this mailing list has been of great assistance, these modifications that I am attempting, and I am sure I will probably need more.
It looks like changing the osname is not the way to do what I need done.
I am still working on getting the symlink support going but there are significant implications to using symbolic links on OpenVMS once the ECO kit is available.
Perl is affected by this, so here is a preview:
Symbolic links introduce and for some operations require the use of a new UNIX style filename convention that is being called POSIX format.
The processing of these specifications is now done by RMS and not by the CRTL so there is a way to use them with almost all existing OpenVMS programs.
Because of the differences in processing a symbolic link references, any program that does it's own translation of file specifications from UNIX format to OpenVMS native format will not return the right answer for symbolic links.
The CRTL will have a new feature setting to indicate when the user has selected that UNIX style pathnames should be parsed in POSIX style, and while I can easily test for this in the C code, but it looks like I would need a way to let the .PM scripts know that this feature has been activated by the user in order to for the special cased OpenVMS code to work with symbolic links.
The perl absolute path routine is one of the ones that is affected by this as it is special cased for OpenVMS to do a manual parse of the filename.
It looks like the way to do that is to have the affected scripts look up the setting of the DECC feature logicals while they run.
-John [EMAIL PROTECTED] Personal Opinion Only
