Front page | perl.perl5.porters |
Postings from November 2007
Andy Lester wrote: > > On Nov 28, 2007, at 8:22 AM, Gerard Goossen wrote: > about kurila and EPCDIC. > OK, but what about the VMS part? That's really the key question: How > much simpler does the code get by removing VMS support? > > Yes, I understand it's academic at this point. The VMS support in perl is mainly three parts: 1. Compensating for current and past bugs/omission in the C library. These would still be needed in kurila, but would show up as a separate library. It is possible to rig the build environment so that this library can be linked in with out modifying the UNIX build procedure. 2. Providing support for the ODS-2 file system. This is a file system that only supports uppercase filenames of 39.39 characters and a few punctuation characters of C<$> C<-> C<_>. Only one period is allowed with up to 39 characters on either side. No periods in directories. Perl also simulates that the ODS-2 file system is lowercase only. There are already existing programs that will not work on ODS-2 file systems. So kurila would still be usable on VMS with out that support. 3. Support for the VMS specific syntax. The VMS C library (except for bugs) will auto convert from UNIX syntax to VMS syntax, so kurila would be usable on VMS with out this support. So removing VMS specific code from kurila might not even be noticed on a build for VMS. Can I use rsync to keep a directory tree up to date if I can find the time to try a build? What is the syntax to pull it? -John wb8tyw@qsl.net Personal Opinion OnlyThread Previous | Thread Next