At 07:53 PM 8/10/00 +0200, Bart Lateur wrote:
>p.s. I've always disliked the word "throwing" for errors, just to be a
>complement to "catch". An error to me is something like a trapdoor,
>where you unexpectedly fall through.
The only difference is the direction of travel :-) In both cases you do
> > Currying placeholders are scalars
>
> Is that a general truth?
Yes. It proceeds from the fact that $_[0], $_[1], ect are scalars.
> It wasn't obvious from RFC 23... If you
> rev it, perhaps you could make that clearer.
Will do.
> Looking back, the defining exampl
Damian Conway wrote:
>> I find nothing in the documentation that suggests that => is
>> anything other than a plain comma operator, yet you call it a
>> "first-argument-stringifying comma operator". In fact, the
>> documentation explicitly claims "=>" is a synonym of "," (see
>
Peter Scott wrote:
>
> try {
> } catch Exception::IO with {
> } catch Exception::Socket with {
> } otherwise {
> };
Jonathan Scott Duff wrote:
>
> try {
> } catch {
> switch ($EXCEPTION->name) {
> case IO { ... }
> case Socket { ... }
>
At 10:33 PM 8/10/00 +0100, Graham Barr wrote:
>On Thu, Aug 10, 2000 at 04:34:50PM -0400, Chaim Frenkel wrote:
> > Nice.
> >
> > The continue clause, I assume would re-raise an uncaught exception.
> > But, a big but. How does the 'else' clause indicate that the exception
> > was handled?
>
>By not
As a casual VMS user, I've always liked the way that VMS coded its error
messages. Perhaps a similar technique could be adopted for perl.
Each message has 4 parts:
Facility:
This is the thing that is reporting the error
Severity:
This is a severit
At 07:29 PM 8/10/00 -0700, Glenn Linderman wrote:
>Thanks for the clarification in your intentions, but isn't _any_ bareword is
>converted to a string, unless it is in some particular context where a
>bareword is
>meaningful (such as filehandle)? So that seems to be nothing unique to
>=>. You
> "PS" == Peter Scott <[EMAIL PROTECTED]> writes:
>> =head1 TITLE
>>
>> All perl generated errors should have a unique identifier
PS> This looks awfully similar to RFC 80. Certainly the exception objects RFC
PS> 80 is thinking about can well have unique numeric attributes.
>> All perl ge
Peter Scott wrote:
> So I'm thinking:
>
> eval { ...
> } catch Exception::Foo {
>...
> } catch Exception::Bar, Exception::Baz {
>...
> } catch {
>... # everything else, but if this block is absent, uncaught exceptions
># head up the call stack
> } continue {
>... # Executed
Glenn Linderman wrote:
> Thanks for the clarification in your intentions, but isn't _any_ bareword
is
> converted to a string, unless it is in some particular context where a
bareword is
> meaningful (such as filehandle)? So that seems to be nothing unique to
=>. You
> could just as well say
>
>
One thing that isn't addressed in any of the exception RFC's (and it
may not be appropriate) is how to actually use it. Not in the syntactical
or semantic meaning. But in how to use it practically.
Given six lines of code within a trapping context, how does one
end up with the invariant restored
Chaim Frenkel wrote:
>
> [stuff about exception numbering]
>
> Hmm, I thought I saw another exception RFC pass by.
> Yup, RFC 88, Tony Olekshy <[EMAIL PROTECTED]>
>
> Could you two folks get together and hash this out.
RFC 88 goes to some trouble to seperate exception handling from
exception obje
Bart Lateur <[EMAIL PROTECTED]> writes:
> What's so hard? Subtracting 2 hours and 30 minutes from the official
> referential time (GMT)? Or the Daylight Savings Time rules?
It's not a problem of implementation. It's a problem of semantics due to
the way Perl parses the language.
Suppose you ca
On Thu, 10 Aug 2000, Decklin Foster wrote:
> Syloke Soong <[EMAIL PROTECTED]> writes:
>
> > my $varname type;
>
> The syntax
>
> my $varname : constant; # pun not intended :)
>
> Was brought up earlier (but probably not before this RFC was written).
> Perhaps something similar could
Dan Sugalski wrote:
> The syntax is actually:
>
>my type $varname;
>
> This is in perl 5.6.0. Modifiers go as attributes after the colon:
>
> my Dog $spot : constant = new Dog;
>
Yes. But what about types and attributes within complex types?
- Constant refs vs refs to constants?
- Types o
Peter Scott wrote:
> Have you used strict lately? :-)
No, but the documentation for strict is some of what I reread before making a
fool of myself arguing with Damian, and it says nothing about barewords, as far
as I could read.
Having used it on occasion, I am aware it _does_ have some effect
I'm several days behind on -language due to dodgy home dialups and the
noise and insanity I suffer at the office.
I'm making a valiant attempt to catch up on 700 posts right now, but
would appreciate it if people could email me privately if there's
anything they particularly want to bring to my a
How would this take into account stuff like this:
sysopen(HANDLE, "/etc/motd", O_RDWR|O_CREAT, 0644);
The "O_RDWR|O_CREAT" part is what I'm talking about here. This is a
constant w/o suffix. We'll either have to:
1. Change it to $O_RDWR|$O_CREAT or $O{RDWR}|$O{CREAT}
Maybe for error
Perl6 RFC Librarian <[EMAIL PROTECTED]> writes, for Chaim Frenkel
<[EMAIL PROTECTED]>:
[...]
> =item As a floating point number
>
> The integer part would be the actual identifier. The fractional
> part could encode some classification scheme.
Floating point numbers don't work this way. Supp
Chaim Frenkel <[EMAIL PROTECTED]> writes:
> Okay, then for
>
> reduce &avg $identity, @list
>
> What should $identity be?
This was my first point regarding C -- not all functions have
an identity element. One should note that in general
(reduce &avg $x,@list) != (reduce &sum 0,@lis
> "AS" == Ariel Scolnicov <[EMAIL PROTECTED]> writes:
AS> 2. Error codes as digit strings with decimal point. So "123.4567"
AS>(_not_ 123.4567) represents error 4567. People will still try
AS>stupid floating-point math tricks to get at the suberror code, but
AS>at least
On Thu, Aug 10, 2000 at 11:12:28AM +0200, Johan Vromans wrote:
> Of course, we need group names (trivial), and group temporaries.
> I needed the latter to define a generic pattern to match quoted strings:
> you need to store the starting quote somewhere to find the ending quote,
> but I didn't wan
On Thu, Aug 10, 2000 at 07:04:50AM -0400, Ilya Zakharevich wrote:
> $quoted = qr/(['"]).*?\2/;
> @a = $str =~ /($quoted)/gp;
>
> Here //p is the "postponed" flag. Put (?p{$quoted}) instead of
> $quoted to get this semantic now (or some other char).
$quoted = qr/(['"]).*?\1/;
@a = $str =~ /(
On Thu, Aug 10, 2000 at 10:16:12AM +0200, Johan Vromans wrote:
> > "(" (.) group(1, [[ 'a' .. 'z' ]] (*) [3,5] ) (.) ")"
> >
> > here (.) is the ASCII substitution for the UNICODE "REx concatenate"
> > char, similarly for [[. ]] and (*). (The chars may be borrowed from
> > the math repertoire.
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Make operators behave consistently in a list context
=head1 VERSION
Maintainer: Jeremy Howard <[EMAIL PROTECTED]>
Date: 10 August 2000
Version: 1.00
Mailing List: [EMAIL PROTECTED]
Number: 82
=he
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Make constants look like variables
=head1 VERSION
Maintainer: Jeremy Howard <[EMAIL PROTECTED]>
Date: 10 August 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 83
=head1 ABSTRACT
This RF
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
The AUTOLOAD subroutine should be able to decline a request
=head1 VERSION
Maintainer: Leon Brocard <[EMAIL PROTECTED]>
Date: 10 Aug 2000
Version: 2
Mailing List: [EMAIL PROTECTED]
Number: 8
=hea
[EMAIL PROTECTED] writes:
: It is proposed that a new syntax for declaring constants be introduced:
:
: my constant $PI = 3.1415926;
: my constant @FIB = (1,1,2,3,5,8,13,21);
: my constant %ENG_ERRORS = (E_UNDEF=>'undefined', E_FAILED=>'failed');
Can't put a modifier like "constant" in the
On Thu, Aug 10, 2000 at 04:47:33PM -, Perl6 RFC Librarian wrote:
> cope with a method call, it should return undef. Perl would then walk
> the OO hierarchy and find the next AUTOLOAD to call, eventually failing
> with an error if no AUTOLOAD method is found which will accept the
> call.
Why n
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Lazily evaluated list generation functions
=head1 VERSION
Maintainer: Jeremy Howard <[EMAIL PROTECTED]>
Date: 10 August 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 81
=head1 ABSTRACT
> "PRL" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes:
PRL> Instead of calling the right thing or actually doing the right thing,
PRL> AUTOLOAD subroutines should return a coderef which will be run as if
PRL> it were the method called. If an AUTOLOAD subroutine does not wish to
PR
On Thu, Aug 10, 2000 at 04:42:56AM -0400, Ilya Zakharevich wrote:
> These are just user-defined ops. You should be able to overwrite the
> normal ops, as in:
>
> sub match_all {
> use re_ops 'overload_usual_ops';
> "(" . group(1, [ 'a' .. 'z' ] * [3,5] ) . ")"
> }
>
> Will this go?
On Wed, Aug 09, 2000 at 04:20:32PM -0400, Ilya Zakharevich wrote:
> It is not clear though how to design concise-but-no-line-noise
> notation for \w etc. But qr/ \( ( [a-z]{3,5} ) \) / may become
>
> "(" (.) group(1, [[ 'a' .. 'z' ]] (*) [3,5] ) (.) ")"
>
> here (.) is the ASCII substitution
Volume on perl6-language is so high, I didn't notice the thread on
RFC 64 until today. That's really the kind of discussion I'm looking
for over (t)here, so I hereby declare RFC 64 as open game for more
focused discussion on perl6-language-strict and request people discuss
it over here in the
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Exception objects and classes for builtins
=head1 VERSION
Maintainer: Peter Scott <[EMAIL PROTECTED]>
Date: 9 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 80
=head1
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Controllable Data Typing
=head1 VERSION
Maintainer: Syloke Soong <[EMAIL PROTECTED]>
Mailing List: [EMAIL PROTECTED]
Date: 10 Aug 2000
Version: 1
Number: 89
=head1 ABSTRACT
Provide a choice for
Michael Fowler wrote:
> > > Which then raises a few more problems (whew): how do you coax user input
> > > (which is an SV) into a value $foo can accept with very-strict on?
> >
> > You run it through an explicit conversion process, like using C in
> > a C program
>
> Unfortunately, this involv
I couldn't determine if this involves just language, or just internals, so
I'm posting to both. Let me know if this discussion is inappropriate for
one or the other (or both?!).
On Thu, Aug 10, 2000 at 05:08:39AM +, David L. Nicol wrote:
>
> The other advantage of typed languages is that t
101 - 138 of 138 matches
Mail list logo
