Attribution lists are getting a bit complex. This is in response to what Piers wrote
on Wed, Dec 18, 2002 at 03:50:44PM +.
DKS
> > [specifying types]
> > Hm. I'm way short on sleep today, so I'm probably missing something,
> > but I don't see why Perl can't sort this out without a specific
On Wed, Dec 18, 2002 at 09:31:41AM +, Piers Cawley wrote:
> Dave Storrs <[EMAIL PROTECTED]> writes:
> > It seems like Perl6 is moving farther and farther away from Perl5's
> > (almost) typelessness.
>
> It depends what you mean by typed. Perl has always had
On Mon, Dec 16, 2002 at 03:44:21PM -0500, Dan Sugalski wrote:
> At 11:12 AM -0800 12/16/02, Dave Storrs wrote:
> >You find R2L easier to read, I find L2R
> >easier. TIMTOWDI. Perl6 should be smart enough to support both.
>
> Why?
>
> Yes, technically we can do bo
On Mon, Dec 16, 2002 at 08:26:25PM +, Piers Cawley wrote:
> Dave Storrs <[EMAIL PROTECTED]> writes:
> > On Mon, Dec 16, 2002 at 06:47:39PM +, Piers Cawley wrote:
> >> Michael Lazzaro <[EMAIL PROTECTED]> writes:
> I haven't been arguing against his syn
On Mon, Dec 16, 2002 at 06:47:39PM +, Piers Cawley wrote:
> Michael Lazzaro <[EMAIL PROTECTED]> writes:
>
> > Mind you (purely devil's advocate), I'm not entirely sure the R-to-L
> > syntax truly _needs_ to be in Perl6. It's true I use it all the time,
> > but I can retrain to use L-to-R meth
On Fri, Dec 13, 2002 at 09:32:02AM -0800, Michael Lazzaro wrote:
>
> $obj.ID;
> $obj.IDENTITY;
FWIW, I favor the latter.
--Dks
On Fri, Dec 13, 2002 at 09:49:44AM -0600, Garrett Goebel wrote:
> Other common names for the proposed .id are:
>
> UUID: Universal Unique Identifier (DCE)
> GUID: Globally Unique Identfier (EFI)
>
> Of the 2, usage of "GUID" seems to be more common IMHO. Both of the above
> are identical in imple
On Fri, Dec 13, 2002 at 09:56:15AM -0500, John Siracusa wrote:
> Using the method/attribute named "id" for "this is the same object"
> comparisons is just plain bad Huffman coding. The "this is the same object"
> method/attribute should have a name that reflects the relative rarity of its
> use.
On Thu, Dec 12, 2002 at 09:39:18PM -0500, James Mastros wrote:
> On 12/12/2002 8:07 PM, Larry Wall wrote:
> > Ordinarily you'd test for subs with one of
> >
> > exists &Main::foo
> > &Main::foo.exists
> I thought that was now spelt exists %Main::{&foo} -- that the symbol
> tables were now
On Wed, Dec 11, 2002 at 02:54:18PM -0800, Dave Whipp wrote:
> "Michael Lazzaro" <[EMAIL PROTECTED]> wrote:
> > After thinking about it a little more, I'll set myself on the "yes"
> > side. And propose either '===' or ':=:' to do it.
>
> Definitely '==='.
Hopefully, this thread has been settled
On Thu, Dec 12, 2002 at 10:35:47AM +1100, Damian Conway wrote:
> Dave Storrs wrote:
> > - the ability for the programmer to set "limiters" (??better name??)
> > on the junction, which will specify how the junction should
> > collapse--e.g. always collapse to the l
On Wed, Dec 11, 2002 at 12:13:49PM -0700, Luke Palmer wrote:
> [Dks wrote:]
> > So...are we intending that types and type safety will be like 'use
> > strict' (optional and only on request), or will they be like sigils
> > (mandatory, can't be turned off)? Or, perhaps, on by default but able
> >
On Tue, Dec 10, 2002 at 10:37:10PM -0700, Luke Palmer wrote:
> Why use regexen when you can just use junctions?
>
> my $foos = 'foo' ~ any(0..9) ~ any(0..9);
At what moment does a junction actually create all of its states?
Hmm...perhaps a clearer way to say that is "At what moment does a
ju
On Mon, Dec 09, 2002 at 03:58:54PM -0700, Luke Palmer wrote:
> > From: Dave Storrs <[EMAIL PROTECTED]>
> > My understanding was that in Perl6, you could use pretty much anything
> > for a hashkey--string, number, object, whatever, and that it did not
> > get mashed d
On Tue, Dec 10, 2002 at 03:38:58PM -0800, Rich Morin wrote:
> On occasion, I have found it useful to cobble up a "little language"
> that allows me to generate a list of items, using a wild-card or some
> other syntax, as:
>
> foo[0-9][0-9] yields foo00, foo01, ...
>
> I'm wondering whether Pe
On Sun, Dec 08, 2002 at 09:35:16PM -0800, Dave Whipp wrote:
> is to use an alphabetic name (e.g. || vs or). perhaps the we
> could name this operator C: its vaguely remenicent of the
>
>@out = @in
>pp map { foo }
>pp grep { bar }
>pp sort { $^a <=> $^b }
I like the id
On Sat, Dec 07, 2002 at 01:28:41PM +1100, Damian Conway wrote:
> Dave Whipp wrote:
>
> > I notice everyone still want Int context for eval of the block:
> > Pease don't forget about hashes. Is there such a thing as
> > 'hashkey context'?
>
> I doubt it. Unless you count Str context.
My understan
On Wed, 30 Oct 2002, Larry Wall wrote:
> If no one saw them then it could well be a problem on my end.
> I'm trying to use a mailer (pine) that doesn't know about UTF-8 in
>
> @a «+» @b
I'm using Pine 4.33 on FreeBSD 4.3, and I see these fine.
--Dks
On Wed, 30 Oct 2002, Graham Barr wrote:
> On Wed, Oct 30, 2002 at 01:57:00PM -0800, Dave Storrs wrote:
> > *shrug* You may not like the aesthetics, but my point still
> > stands: "is rw" is too long for something we're going to do fairly often.
>
> I am
On Wed, 30 Oct 2002, Angel Faus wrote:
> Then let's make the parens required when there is more than one
> stream.
>
> Sane people will put them there anyway, and it will force the rest of
> us to behave.
>
> It also solves the ";"-not-a-line-seperator problem.
>
> -angel
Yes! Thank y
On Thu, 31 Oct 2002, Damian Conway wrote:
> Dave Storrs wrote:
>
> > Actually, yes, that would solve everything for me...and I knew
> > this was valid syntax.
>
> So is this vertical layout, which I think will become fairly standard
> amongst those who care about
On Wed, 30 Oct 2002, Austin Hastings wrote:
>
> --- Dave Storrs <[EMAIL PROTECTED]> wrote:
>
> > for @a -> $x<; @b -> $y { $x = $y[5] };
>
> Yes!!!
>
> (Except for the '<'. That's feigen-ugly.
*shrug* You may not like the aes
On Wed, 30 Oct 2002, Michael Lazzaro wrote:
> On Wednesday, October 30, 2002, at 12:48 PM, Dave Storrs wrote:
> > for @a; @b -> $x is rw; $y { $x = $y[5] };
>
> I agree that it's an eyeful. How many of your issues could be solved
> if the above were just wri
In a different thread, Buddha Buck wrote the following code snippet:
for @a; @b -> $x is rw; $y { $x = $y[5] };
And I finally had to whimper publicly about this.
I've been lurking around the P6 process since the very beginning of the
RFC process. I saw the new 'for' syntax come out, and
In the "Re: Wh<[ie]>ther Infix Superposition ops" thread
On Wed, 30 Oct 2002, Piers Cawley wrote:
> But given a decent Collection hierarchy:
>
> my $seen = Set.new($start,$finish);
>
> for <> -> $next {
> print $next unless $next =~ $seen;
> $seen.insert($next);
> }
or hairy fishnuts" reference in
here somewhere, but I can't quite make it work.
Dave Storrs
e of 8, but $a = $a + 3 leaves it with a
value of 9.
Dave Storrs
Ah! Ok, yes, I had missed that. Thanks, this is exactly what I wanted.
Dave
On Mon, 5 Aug 2002, Stephen Rawls wrote:
> >> Doesn't the :w option do that?
> >> :w/one two/ translates to /one \s+ two/
>
> >Not exactly. The regex you showed would match any of these (using
> underscores for
>
On Sat, 3 Aug 2002, Ken Fox wrote:
> Dave Storrs wrote:
> > why didn't you have to write:
> >
> >rule ugly_c_comment {
> >
> /
> >
> \/ \* [ .*? ? ]*? \* \/
> >
> { let $0 := " " }
>
e. Why is
this replacement necessary...isn't it sufficient to simply define it as
whitespace, as was done above?
Dave Storrs
On Fri, 7 Jun 2002, Luke Palmer wrote:
> > Dave Storrs wrote:
> > Can we please have a 'reverse x' modifier that means "treat whitespace as
> > literals"? Yes, we are living in a Unicode world now and your data could
> >
> > /FATAL ERROR\:
On Mon, 10 Jun 2002, Larry Wall wrote:
> On Mon, 10 Jun 2002, Dave Storrs wrote:
>
> >
> > I assume that 'fatal.pm' is a new pragma.
>
> Already exists for Perl 5, actually.
*blush* Must have missed it. Drat, and I just finished rereading
Camel III. Apologies.
Dave
t I'd check.)
Dave
On Fri, 7 Jun 2002, Larry Wall wrote:
> On Fri, 7 Jun 2002, Dave Storrs wrote:
> > Just to be sure I understood: you meant that (A) yes, you can use
> > fail in a subroutine outside a regex, and (B) if you do, it is no
> > different from die.
On Fri, 7 Jun 2002, Damian Conway wrote:
> Dave Storrs wrote:
>
> > Somehow, this feels like we're trying to roll all of Prolog
> > into Perl,
>
> No. We're rolling in all of yacc/lex/RecDescent instead. ;-)
And this should reassure me _why_?
Well, A5 definitely has my head spinning. The new features seem amazingly
powerful...it almost feels like we're going to have two equally powerful,
equally complex languages living side-by-side: one of them is called
"Perl" and the other one is called "Regexes". Although they may talk to
one an
On Tue, 4 Jun 2002, Luke Palmer wrote:
> On Tue, 4 Jun 2002, Miko O'Sullivan wrote:
>
> > No configuration files (.e.g .cpan) are necessary. However, you can use a
> > configuration file if you want tp indicate a .cpan-like file
> >
> >cpan --conf ~/.cpan load Date::EzDate
>
> What about n
[Several people said something like "$var is rw will do it")
Ah, that's right. I had forgotten about this.
Thanks to everyone who responded.
Dave
ould confuse people into thinking that they will need to
manually dereference the variable, which they shouldn't need to do.
Is there a way to do this now? If not, will there be a way in
Perl6?
Dave Storrs
t to mean "skip over
> the following" rather than "skip to the following"), but I find "nobreak" also
> a bit strange. How about "proceed"?
>
> Ted
First, a 'me too' to everything Ted said.
Second, to me 'nobreak' is not sufficiently visually distinct from
'break'.
Dave Storrs
only thing to the left of ->
is a scalar, it could reduce to this (in Perl5 terms):
# This Perl6:
for $_ -> $x { ... }
# is the same as this Perl5:
{
my $x = $_;
local ($_);
{ ... }
}
Dave Storrs
=head1 TITLE
API for the Perl 6 debugger.
=head1 VERSION
1.1
=head2 CURRENT
Maintainer: David Storrs ([EMAIL PROTECTED])
Class: Internals
PDD Number: ?
Version: 1
Status: Developing
Last Modified: August 18, 2001
PDD Format: 1
Language: English
=head2
e native numbers, does it support threads and (if so) what
threading model (though this is probably a moot point in P6, perhaps it
is something that could be included into 5.8.x).
Dave Storrs
The Dragon Book is (AFAIK) still considered the definitive book on the
subject. It's called that because it has (or at least, had, for the
edition that I bought) a red dragon on the cover.
The official title is:
Compilers : Principles, Techniques, and Tools
by Alfred V. Aho, Ravi Sethi, Je
On Sun, 22 Jul 2001, Johan Vromans wrote:
> Dave Storrs <[EMAIL PROTECTED]> writes:
>
> > I discovered today that I had forgotten to put 'use strict' at the top of
> > one of my modules...it was in the script that _used_ the module, but not
> > in the
On Sat, 21 Jul 2001 [EMAIL PROTECTED] wrote:
> On Sat, Jul 21, 2001 at 02:47:43PM -0700, Dave Storrs wrote:
>
> > It would be nice if there was a
> >
> > use strict 'recursive';
> >
> > option that you could set in a script or module (pa
On Sat, 21 Jul 2001, Dan Brian wrote:
> > The debugger API PDD that I submitted a couple of days ago suggested that
> > we incorporate a profiler into the core. What do people think of this
> > idea?
>
> I think that with a clean API, many third-party profilers could and would
> be created. I
First topic:
I discovered today that I had forgotten to put 'use strict' at the top of
one of my modules...it was in the script that _used_ the module, but not
in the module itself. Putting it in instantly caught several annoying
bugs that I'd been trying to track down.
It would be nice if ther
On Tue, 10 Jul 2001, Michael G Schwern wrote:
> We could assume untyped variables are untyped, but I'd rather they're
> considered mistakes. Again, the purpose here is to catch mistakes. I
> don't know if this will wind up being more or less annoying, we'll
> have to play with it a little. F
On Mon, 11 Jun 2001, Daniel S. Wilkerson wrote:
> For example, the
> "going back in time and preventing your grandparents from having sex"
> situation.
Bah, who needs sex these days? A little in vitro here, a little
cloning with genetic tweaking there...a whole new person, no sex inv
On Thu, 7 Jun 2001, Michael G Schwern wrote:
> On Wed, Jun 06, 2001 at 01:37:23AM -0500, Me wrote:
> > > B&D languages
> >
> > What's B&D?
>
> Bondage and Discipline, scum! You're not a good enough programmer to
> be trusted not to make mistakes! Now drop and give me fifty!
Hmmm...
On Fri, 8 Jun 2001, Chris Hostetter wrote:
> After reading the Apocalypse & Exegesis articles, and seeing some examples
> of properties and the "is" operator, I'd like to suggest that the
> less-then operator be changed, so it is functionally equivalent to:
>
> $v2 = VALUE2;
> $v1
On Tue, 5 Jun 2001, Michael G Schwern wrote:
> On Tue, Jun 05, 2001 at 01:34:35PM -0700, Daniel S. Wilkerson wrote:
> > I cannot imagine running an enterprise critical application
>
> As a complete digression, can we please strike the term "enterprise"
> from the English lexicon? Completely r
On Tue, 5 Jun 2001 [EMAIL PROTECTED] wrote:
> So I'd say no, Perl can't know at compile-time if your method is
> declared or not. Only in certain restricted cases, such as if you
> don't inherit from anything, or if *all* your parent classes are
> declared strictly.
(By 'strictly', I
On Tue, 22 May 2001, Graham Barr wrote:
> On Tue, May 22, 2001 at 12:29:33PM +1000, Damian Conway wrote:
> >
> > We actually want the possibility of that kind of namespace collision:
> > for polymorphism.
>
> Many people keep bringig this up as a confusion and you give the same reply.
>
> Wi
On Mon, 21 May 2001, Jonathan Scott Duff wrote:
> On Mon, May 21, 2001 at 10:01:28AM -0700, Dave Storrs wrote:
>
> Would you also advocate separate declarative syntax for variable
> properties and value properties? That's where I think much confusion
> will be.
On Mon, 21 May 2001, Jonathan Scott Duff wrote:
> So, if I have a Dog $spot, here's a little table where a 1 in the M
> column means $spot has a bark method that says 'woof', 1 in the V column
> means $spot has a bark variable (compile-time) property that says 'arf'
> and a 1 in the A column me
On Fri, 18 May 2001, Nathan Wiger wrote:
> Maybe there are two different features being conflated here. First, we
> have "is", which is really for assigning permanent properties:
>my $PI is constant = '3.1415927';
> So, those make sense, and we'd want them to remain through assignment.
>
I recently received the following email from someone whose name I
have snipped.
> * Dave Storrs <[EMAIL PROTECTED]> [05/16/2001 08:11]:
> >
> > Ok, this is basically a bunch of "me too!"s.
>
> Keep the snide comments to yourself. Thanks.
Ok, this is basically a bunch of "me too!"s.
On Tue, 15 May 2001, Nathan Wiger wrote:
> Awesome. Simple, Perlish, easy to read, etc. Also, I see you took the
> suggestion of:
>
>Access through... Perl 5 Perl 6
>= == ==
>Array
On Tue, 15 May 2001, Simon Cozens wrote:
> On Tue, May 15, 2001 at 03:30:07PM -0700, Dave Storrs wrote:
> > - A while ago, someone suggested that the word 'has' be an alias
> > for 'is', so that when you roll your own properties, you could write
> &
First of all: Damian, thank you for putting this together. This is a
really good way to dispell the concerns/doubts/pick-a-word that people
(including myself) have been having about whether Perl6 would be the
language that we all know and love.
There was a great deal of stuff in there and I
All that follows is merely MHO, so feel free to disregard.
On Fri, 11 May 2001, Nathan Wiger wrote:
> Well, I think we should take a step back and answer a few key questions:
>
> 1. Do we want to be able to use Perl 5 modules in a
>Perl 6 program (without conversion)?
On Fri, 11 May 2001, Larry Wall wrote:
> Dave Storrs writes:
> : calling the function that produced the string, or whatever. I just think
> : that we could extend 'x' to have a general repetition meaning.
>
> I think just patching one operator from verbal status to
On Thu, 10 May 2001, Larry Wall wrote:
> Dave Storrs writes:
> : should stick with <>. Also, I'd prefer to use the 'x' operator for
> : specifying multiples:
> :
> : @foo = <$STDIN> x 4;
> : @foo = <$STDIN> x &mySub;
> :
On Thu, 10 May 2001, Uri Guttman wrote:
> >>>>> "DS" == Dave Storrs <[EMAIL PROTECTED]> writes:
>
> DS> There have been multiple mentions of the fact that we intend to have safe
> DS> signals in Perl 6. I was wondering if it will also be p
< QUOTE LARRY >
Dave Storrs writes:
: You know, it would be really cool if you specify the number of
: lines you wanted like so:
:
: <$STDIN # One line
: *<$STDIN# All available lines
: *4<$STDIN # Next 4 lin
There have been multiple mentions of the fact that we intend to have safe
signals in Perl 6. I was wondering if it will also be possible to have
more than one alarm() set at a time, or some other mechanism for having
multiple pending signals.
Dave
On Tue, 8 May 2001, Me wrote:
> yes?
>
> And, despite perl5's use of no as the opposite
> of use, and given that there may be no use in
> perl6 (;>), and thus perhaps no no, (on and off?),
> then maybe no could be used as not yes?
>
> no?
Your Honor, I would like to stipulate that t
On Tue, 8 May 2001, Larry Wall wrote:
> In this view, * and < could just be two different kinds of "expandable" flags.
> But I'm uncomfortable with that, because I'd like to be able to say
>
> lazy_sub(<$STDIN, <$STDIN, <$STDIN, <$STDIN)
>
> to feed four lines to lazy_sub without defeati
On 3 May 2001, Ilya Martynov wrote:
> >> You can serialize/deserilize object with Storable
> >>
> >> $foo = new Bar
> >> store_fd $foo, \*SOCKET;
> >>
> >> and on the other end
> >>
> >> $foo = retrieve_fd \*SOCKET;
> >> $foo->bar;
> >>
> >> It will work if you have Bar module on both ends.
On Wed, 2 May 2001, Dan Brian wrote:
> Another snippet from the .NET whitepaper:
>
>
> Everyone believes the Web will evolve, but for that evolution to be
> truly empowering for developers, businesses, and consumers, a radical new
> vision is needed. Microsoft's goal is to provide that vision
For those of us who came in late...I gather that -> is expected to be
replaced by '.', which means that we need to find something else for '.'.
Somehow, however, I missed out what the exact benefits are of this
replacement--I'm not saying that there *aren't* any, I just never saw the
message whe
On Mon, 9 Apr 2001, Peter Scott wrote:
> At 09:36 AM 4/9/01 +0200, Ariel Scolnicov wrote:
> >
> >One liners are supposed to be SHORT. `--cmd' is LONG. If we MUST go
> >the multiflagged way, why not reflect `-e' to get the `-6' flag? At
> >the very least, I want a short flag!
>
> But by the
On Thu, 5 Apr 2001, John Porter wrote:
> Nathan Wiger wrote:
> > the more compatible
> > with Perl5 Perl6 is, the more likely it is to be accepted.
>
> I don't believe that's necessarily true.
> If Perl6 proves to be a significantly better Perl than Perl5,
> people will adopt it, especially if
On Thu, 5 Apr 2001, Nathan Wiger wrote:
> I'm unsure about the "module main" idea. I like that modules as a whole
> are strict/-w by default. But the "module main" tag causes the same
> problem Larry is opposed to with BASIC/PLUS "EXTEND". That is, every
> Perl 6 program begins with "module mai
On Sun, 4 Feb 2001 [EMAIL PROTECTED] wrote:
> >>>>> "Dave" == Dave Storrs <[EMAIL PROTECTED]> writes:
>
>
> Dave> When you want to install a new version, you simply prepend it
> Dave> with its version number (or insert it at appropriate pl
On Fri, 2 Feb 2001, Garrett Goebel wrote:
> $Foo::VERSION eq 1.00
> |
> | $Foo::VERSION eq 2.00
> | |
> Bar Baz
> \ /
> My::Module
Ideally, it should be perfectly legit to have multiple versions of
a given module on your system, which would resolve this problem nicely.
On Tue, 30 Jan 2001, Nathan Wiger wrote:
> Jarkko Hietaniemi wrote:
> >
> > As I said the problem isn't the p52p6 doing that kind of transformation.
> > The problem is someone familiar with perl5 writing code in perl6:
> >
> > if (my $fh = open(">/tmp/$$".time())) {
> >
> > and later
On 29 Sep 2000, Piers Cawley wrote:
> Is it possible? Advisable?
I haven't seen it yet, but that doesn't mean it's not in there
somewhere...there's a bunch of RFCs I haven't had time to read. If it
isn't there, it should be. I think this is definitely a cool idea.
On Wed, 27 Sep 2000, Johan Vromans wrote:
> What I wanted to indicate is that the input and output handling of the
> debugger, currently line input and line output, should not be turned
> into a sophisticated user interface with command line recall/editing
> and fancy output paging (e.g. two in
On 26 Sep 2000, Johan Vromans wrote:
> Perl6 RFC Librarian <[EMAIL PROTECTED]> writes:
>
> > The ability to easily retrieve and edit your N most recent commands to the
> > debugger (much like a bash_history).
> and
> > A better default pager. The default pager should assume a 24x80 term
> > win
I personally have never had problems with these issues and would just as
soon that this RFC didn't do through. However, I don't feel particularly
strongly about most of it. Specifically:
As to autoquoting the lefthand side of -> (thereby making it a class
name), I don't particularly care.
The
On Mon, 25 Sep 2000, Michael Fowler wrote:
> This RFC makes no mention of what happens to the following constructs:
>
> %foo = (bar => "baz");
This actually isn't a bareword (as I understand it), since the =>
operator quotes its
LHS.
On Sun, 24 Sep 2000, Nathan Wiger wrote:
> > Offer simple functions to set HTTP headers (e.g. content type, result codes)
> How about %HTTP, which is just flushed on the first line of output?
>use cgi;
>$HTTP{'Content-type'} = 'text/html';
>print "Hello!"; # flushes %HTTP first
On 25 Sep 2000, Perl6 RFC Librarian wrote:
> =head1 TITLE
>
> Remove -X
>
> The prefered mechanism for file tests should be more legible, using
> terms like 'readable(FOO)' and 'writeable(FOO)' instead of the
> =head1 MIGRATION ISSUES
> Perl programmers happy with the -X syntax will need to
On Sat, 23 Sep 2000, raptor wrote:
> > On Thu, 21 Sep 2000, Tom Christiansen wrote:
> >
> > > =item perl6storm #0050
> > >
> > > Radical notion: consider removing precedence.
> > > Wrong precedence makes people miserable.
> What if we have these 2 rules or no rules AND we can set manualy the
>
On Fri, 22 Sep 2000, Greg Boug wrote:
> > > =item perl6storm #0064
> > >
> > > Do something about microsoft's CRLF abomination.
>
> Perhaps somehow allowing $/ to take multiple input delimeters (perhaps in a
> fashion similar to egrep)... How about:
[snip]
> $/ = "seperator1|seperator2"
On Wed, 20 Sep 2000, Eric Roode wrote:
> foo();
> print $x;
>
> Generate a warning, or not? Which one? Remember, foo() may initialize $x.
My suggest (FWIW) would be that, if there is no execution path
which leads to $x being defined in the second line, then a "Use of
uninit'
On Wed, 20 Sep 2000, Steve Fink wrote:
> 1 my ($x, $y, $z);
> 2 $z = 1;
> 3 my $logfile = "/tmp/log";
> 4 $x = 1 if cond();
> 5 print $x+$y;
> 6 undef $z;
> 7 print $z;
>
> --> use of uninitialized variable $y in line 5 (compile time)
> --> possible use of uninitialized variable $x in line 5 (
On Tue, 19 Sep 2000, Tom Christiansen wrote:
> >This RFC proposes that the internal cursor iterated by the C function
> >be stored in the pad of the block containing the C, rather than
> >being stored within the hash being iterated.
>
> Then how do you specify which iterator is to be reset when
On Tue, 19 Sep 2000, H.Merijn Brand wrote:
> On 19 Sep 2000 09:23:00 +0300, Ariel Scolnicov <[EMAIL PROTECTED]> wrote:
> >
> > I'm planning to withdraw RFC184 ("Perl should support an interactive
> > mode"), due to lack of interest. There was little discussion of it,
I seem to have m
On Mon, 18 Sep 2000, Michael G Schwern wrote:
> I'm sure there are many times when pack should have been used but it
> got hacked together with something else. The prime example is [...]
I must admit I'm with Michael on this one. I've been writing Perl
on and off for two or three ye
On Fri, 15 Sep 2000, Bart Lateur wrote:
> On Thu, 14 Sep 2000 18:14:49 -0400, Mark-Jason Dominus wrote:
>
> >The perl 5 -> perl 6 translator should [recursively handle eval]
>
> Blech, no. eval should stay eval. People are responsible for generating
> Perl6 compatible code, if they construct
On 14 Sep 2000, Ariel Scolnicov wrote:
> 1. It requires the perl parser know about indentation. Of course we
>all know that tabs are 8 characters wide (I myself make a point of
>bludgeoning anyone who says otherwise), but do we really want to
>open this can of worms?
No, b
On Mon, 11 Sep 2000, John Porter wrote:
> Dave Storrs wrote:
> >
> > init_vars \{name => 'NONE'};
> > my @employees : size 50; # 50 entries, each a ref to 1 elem. hash
> > @employees = get_from_db('*');
> > f
On Mon, 11 Sep 2000, Myers, Dirk wrote:
> >Suppose you could specify the value with which all variables
> >in the enclosing scope should be initialized; for example:
>
> I haven't seen this either, but I suggest that it should be a set of
> pragmas:
> use init_scalar 0 ;
> use init_array () ;
This is something fairly basic, but I haven't seen it in discussion or in
the RFCs. If I've missed it, my apologies.
In Perl 5, when a variable is created, it is given the "undefined" value.
This can lead to lots of spurious "Use of uninit'd variable" warnings.
Suppose you could specify the val
On Thu, 24 Aug 2000, Bart Lateur wrote:
> On Mon, 21 Aug 2000 18:21:00 -0700 (PDT), Larry Wall wrote:
> >If you want to save the world, come up with a better way to say "www".
> >(And make it stick...)
>
> "The world"? This problem only exists in English!
>
> We pronounce it something similar
On Fri, 18 Aug 2000, Jonathan Scott Duff wrote:
> On Fri, Aug 18, 2000 at 10:39:36AM -0500, Brian Wheeler wrote:
> > "Using" might be an interesting alternative
>
> Reminds me of BASIC :-)
Works for me.
> > What if the hash keys we want to use are not valid scalar names? For examp
On Thu, 17 Aug 2000, Jonathan Scott Duff wrote:
> BTW, if we define C to map keys of a hash to named place holders
> in a curried expression, this might be a good thing:
>
> with %person {
> print "Howdy, ", ^firstname, " ", ^lastname;
> }
>
> # becomes
> sub {
1 - 100 of 110 matches
Mail list logo
