iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Don't link to the Internet RFCs -- these are Perl RFCs.

This commit is contained in:
Georg Brandl 2007-10-04 06:57:33 +00:00
parent bcf9c4ac0f
commit 70f258a7a1
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
pep-0344.txt
View File

@ -117,7 +117,7 @@ Rationale
As for other languages, Java and Ruby both discard the original As for other languages, Java and Ruby both discard the original
exception when another exception occurs in a 'catch'/'rescue' or exception when another exception occurs in a 'catch'/'rescue' or
'finally'/'ensure' clause. Perl 5 lacks built-in structured 'finally'/'ensure' clause. Perl 5 lacks built-in structured
exception handling. For Perl 6, RFC 88 [9] proposes an exception exception handling. For Perl 6, RFC number 88 [9] proposes an exception
mechanism that implicitly retains chained exceptions in an array mechanism that implicitly retains chained exceptions in an array
named @@. In that RFC, the most recently raised exception is named @@. In that RFC, the most recently raised exception is
exposed for matching, as in this PEP; also, arbitrary expressions exposed for matching, as in this PEP; also, arbitrary expressions

2
pep-3134.txt
View File

@ -117,7 +117,7 @@ Rationale
As for other languages, Java and Ruby both discard the original As for other languages, Java and Ruby both discard the original
exception when another exception occurs in a 'catch'/'rescue' or exception when another exception occurs in a 'catch'/'rescue' or
'finally'/'ensure' clause. Perl 5 lacks built-in structured 'finally'/'ensure' clause. Perl 5 lacks built-in structured
exception handling. For Perl 6, RFC 88 [9] proposes an exception exception handling. For Perl 6, RFC number 88 [9] proposes an exception
mechanism that implicitly retains chained exceptions in an array mechanism that implicitly retains chained exceptions in an array
named @@. In that RFC, the most recently raised exception is named @@. In that RFC, the most recently raised exception is
exposed for matching, as in this PEP; also, arbitrary expressions exposed for matching, as in this PEP; also, arbitrary expressions