New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when do we tidy perlport? #12426
Comments
From @nwc10I 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 I have pushed the commit to blead that deletes all the special case Unlike USA, VM/ESA had mentions in perlport.pod. @@ -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) =item sysopen The traditional "0", "1", and "2" MODEs are implemented with different =item system Notice that an *other* platform that is mentioned as having non-standard So 0) Should perlport represent the current state of Perl portability, or 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 |
From @xdgOn Wed, Sep 19, 2012 at 12:48 PM, Nicholas Clark
I vote "current" -- |
The RT System itself - Status changed from 'new' to 'open' |
From @jkeenanOn Wed Sep 19 09:48:42 2012, nicholas wrote:
...
Perhaps we could extract all the pre-OS X references to the Mac OS from |
From @ap* David Golden <xdg@xdg.me> [2012-09-19 18:55]:
So do I. It might be worth adding a short preamble paragraph about perl having Hmm, considering my suggestion for UTS in perl58delta, I see a pattern Regards, |
From @nwc10On Wed, Sep 19, 2012 at 05:59:42PM -0700, James E Keenan via RT wrote:
Given that Classic is very dead, I don't see any real benefit of this On Thu, Sep 20, 2012 at 10:00:14AM +0200, Aristotle Pagaltzis wrote:
whereas keeping Classic's documentation in does cost us a bit. Nicholas Clark |
From @rjbs* Aristotle Pagaltzis <pagaltzis@gmx.de> [2012-09-20T04:00:14]
I agree with the specific and general both. -- |
From @jkeenanOn Wed Sep 19 09:48:42 2012, nicholas wrote:
Let's see if we can move this RT to resolution. 0) My reading of the contributions to this RT suggest that 1) Which implies that we should remove Mac OS Classic references. 2) Nick, no one responded to you re VM/ESA -- perhaps because no one Thank you very much. |
From @nwc10On Mon, Jan 14, 2013 at 07:09:32PM -0800, James E Keenan via RT wrote:
I didn't know what it is either. The commit message when I removed it was: commit 043fec9 Remove the VM/ESA port. Top Google hit is a wikipedia page that references it in passing. IBM's http://www.vm.ibm.com/vm240/ Both suggest that it was replaced by z/VM Nicholas Clark |
From @jkeenanOn Mon Jan 14 19:09:31 2013, jkeenan wrote:
Nick, et al.: Shall we proceed with this?
Nick, et al.: Shall we proceed with this? Thank you very much. |
From @jkeenanOn Sat Jan 25 18:10:24 2014, jkeenan wrote:
Nick, et. al.: Shall we proceed with this? Thank you very much. |
From @rjbs* James E Keenan via RT <perlbug-followup@perl.org> [2014-05-18T10:26:55]
Yes, we should eliminate perlport documentation of platforms that are not -- |
From @jkeenanOn Mon Sep 15 15:14:31 2014, perl.p5p@rjbs.manxome.org wrote:
This ticket was originally filed in September 2012. At various times I suggested we delete references to two OSes which we knew to no longer be supported. But the consensus of comments has been that we should document which OSes are *currently* supported. That's a significantly different objective, as evidence of active porting to any given OS would be needed to qualify as "currently supported." It's not as simple as "delete references to Mac OS Classic and VM/ESA". Concretely, that would mean that we'd have to replace the section starting "Supported Platforms (Perl 5.8)" with one starting at 5.20 -- correct? If so, how do we gather the evidence we need? Thank you very much. -- |
From @rjbs* James E Keenan via RT <perlbug-followup@perl.org> [2014-09-15T18:51:28]
Yes, this seems about right. My instinct would be to do roughly this: Document each platform as "supported, The evidence is basically the appearance of smoke reports or bug reports one -- |
Migrated from rt.perl.org#114970 (status was 'open')
Searchable as RT114970$
The text was updated successfully, but these errors were encountered: