develooper Front page | perl.perl5.porters | Postings from September 2012

[perl #114970] when do we tidy perlport?

Thread Previous | Thread Next
Nicholas Clark
September 19, 2012 09:49
[perl #114970] when do we tidy perlport?
Message ID:
# New Ticket Created by  Nicholas Clark 
# Please include the string:  [perl #114970]
# in the subject line of all future correspondence about this issue. 
# <URL: >

I mailed this to the list at the time, but it got Warnocked

I'd like at least someone else to consider an answer, so here it is as an RT
ticket. OK, technically someone can close it without commenting, but I don't
forsee that happening. :-)

I have pushed the commit to blead that deletes all the special case
code for VM/ESA, which should escape in a dev release tomorrow.

Unlike USA, VM/ESA had mentions in perlport.pod.
I have deleted them. I'm not *sure* if this was the right thing to do.
Specifically, I did this:

@@ -1975,14 +1971,14 @@ syntax if it is intended to resolve to a valid path.

 =item syscall

-Not implemented. (Win32, VMS, S<RISC OS>, VOS, VM/ESA)
+Not implemented. (Win32, VMS, S<RISC OS>, VOS)

 =item sysopen

 The traditional "0", "1", and "2" MODEs are implemented with different
 numeric values on some systems.  The flags exported by C<Fcntl>
 (O_RDONLY, O_WRONLY, O_RDWR) should work everywhere though.  (S<Mac
-OS>, OS/390, VM/ESA)
+OS>, OS/390)

 =item system

Notice that an *other* platform that is mentioned as having non-standard
O_RDONLY etc is Mac OS. This isn't well phrased. It's Mac OS *classic*.
Likewise, the earlier text in there about \r line endings is *classic*,
not Darwin.


0) Should perlport represent the current state of Perl portability, or
   historical things too?

which probably then answers

1) Should we remove or correct the Mac OS references?

2) Should I have removed the VM/ESA references?

Nicholas Clark

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About