develooper Front page | perl.perl5.porters | Postings from January 2014

[perl #114970] when do we tidy perlport?

Thread Previous | Thread Next
From:
James E Keenan via RT
Date:
January 26, 2014 02:10
Subject:
[perl #114970] when do we tidy perlport?
Message ID:
rt-4.0.18-5314-1390702224-557.114970-15-0@perl.org
On Mon Jan 14 19:09:31 2013, jkeenan wrote:
> On Wed Sep 19 09:48:42 2012, nicholas wrote:
> > 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.
> > 
> > So
> > 
> > 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?
> > 
> 
> Let's see if we can move this RT to resolution.
> 
> 0) My reading of the contributions to this RT suggest that
> pod/perlport.pod ought to "represent the current state of Perl
> portability."  If anyone dissents, please speak up now.
> 
> 1) Which implies that we should remove Mac OS Classic references.
> 

Nick, et al.:  Shall we proceed with this?

> 2) Nick, no one responded to you re VM/ESA -- perhaps because no one
> knows what that is.  (Well, at least *I* don't know what it is.)  Which
> makes a case for removing the reference.  But perhaps you could explain
> a bit more about that?
> 

Nick, et al.: Shall we proceed with this?

Thank you very much.
Jim Keenan

---
via perlbug:  queue: perl5 status: open
https://rt.perl.org/Ticket/Display.html?id=114970

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About