develooper Front page | perl.perl5.porters | Postings from December 2008

Re: RFC: Consolidated proposal for octals like \400 in strings. Was: PATCH [perl #59342] chr(0400)

Thread Previous | Thread Next
From:
Rafael Garcia-Suarez
Date:
December 7, 2008 14:20
Subject:
Re: RFC: Consolidated proposal for octals like \400 in strings. Was: PATCH [perl #59342] chr(0400)
Message ID:
b77c1dce0812071420l30d30d02ja8aba5de2267985f@mail.gmail.com
2008/12/6 Abigail <abigail@abigail.be>:
> On Sat, Dec 06, 2008 at 12:55:58AM +0000, Ben Morrow wrote:
>>
>>
>> If these changes were made 'feature's instead, all people wanting new
>> behaviour would have to do is insert
>>
>>     use 5.012;
>
>
> We went over this some time ago as well. Then it was agreed upon
> that 'use 5.XXX' should not mean anything more than "hey, compiler,
> my code doesn't use any identifiers that may clash with new keywords,
> so feel free to consider them keywords". It most definitely shouldn't
> change the meaning of constructs.

I agree. See feature's manpage:

=head1 NAME

feature - Perl pragma to enable new syntactic features

=head1 DESCRIPTION

It is usually impossible to add new syntax to Perl without breaking
some existing programs. This pragma provides a way to minimize that
risk. New syntactic constructs can be enabled by C<use feature 'foo'>,
and will be parsed only when the appropriate feature pragma is in
scope.

=cut

So it's explicitly stated that feature.pm is for new syntax.
That means that we could use it to enable \o{...} (although I don't
see a necessity), but not for changing existing syntax.

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