On Fri, 29 Sep 2000, Hildo Biersma wrote:
> > Currently, C<\1> and $1 have only slightly different meanings within a
> > regex. Let's consolidate them together, eliminate the differences, and
> > settle on $1 as the standard.
>
> Sigh. That would remove functionality from the language.
>
>
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 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 Wed, 27 Sep 2000, Dan Sugalski wrote:
> At 05:37 AM 9/27/00 +, Perl6 RFC Librarian wrote:
> >Perl should adopt scheme-like symbols, both at the language level
> >and at the internals level.
>
> The explanation of this isn't that clear for me. (I have no scheme
> experience at all)
On Sat, 30 Sep 2000, Bart Lateur wrote:
> I wrote this before, but apparently you didn't hear it. Let me repeat:
You're right, I missed your email when I was incorporating things
into the new version. Apologies.
> $foo on the LHS allows metacharacter matching, for example "a.*b" can
On 27 Sep 2000, Piers Cawley wrote:
> > Do we *want* to maintain \1? Why have two notations to do the
>
> I'm kind of curious about what happens when you want to do, say:
>
> if (m/(\S+)/) {
> $reg = qr{<(em|i|b)>($1)};
> }
>
> where the $1 in the regex quote is refering to $1
On Wed, 27 Sep 2000, Jonathan Scott Duff wrote:
> If $1 could be made to work properly on the LHS of s///, I'd vote for
> that being The Way.
That was pretty much my thought?
On Wed, 27 Sep 2000, Richard Proctor wrote:
> > Both \1 and $1 refer to what is matched by the first set of parens in a
> > regex. AFAIK, the only difference between these two notation is that \1
> > is used within the regex itself and $1 is used outside of the regex. Is
> > there any reason n
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
Is anyone here familiar with the behind-the-scenes process and politics of
the Linux development community?
If I understand it correctly (and I'm not sure I have the details right),
when Linux was being developed, Linus came up with a skeletal OS based off
of MINIX, then he turned it loose. Peop
On Mon, 9 Oct 2000, Nathan Torkington wrote:
> Closed-for-posting mailing lists that are publically readable is the
> best suggestion we've had to meet these ends so far.
>
> Anyone have better suggestions?
I don't know that this is _better_, but...perhaps we could have
the lists that
SARILY to do with the almighty dollar, and stating that it
does is simply clouding the issue.
This thread has gone on for a long time, and is starting to repeat
itself...could we please let it go?
Dave Storrs
On Tue, 21 Nov 2000, Jarkko Hietaniemi wrote:
> Yet another bummer of the current SVs is that they poorly fit into
> 'foreign memory' situations where the buffer is managed by something
> else than Perl. "No, thank you, Perl, keep your greedy fingers off
> this chunk. No, you may not play wit
later.
Dave Storrs
On Mon, 27 Nov 2000, Dan Sugalski wrote:
>int perl6_parse(PerlInterp *interp,
>void *source,
>int flags,
>void *extra_pointer);
On Wed, 29 Nov 2000, Dan Sugalski wrote:
> At 09:51 AM 11/29/00 -0800, Dave Storrs wrote:
> >I have a feeling this is a stupid question, but I have to ask anyway.
> >
> >Do we really need to pass in a PerlInterp pointer? Or can perl6_parse
> >just create one for
help set up the infrastructure.
However, we should move carefully, because it could be a very good thing
or a very harmful thing depending on how we implement it.
So, are other people actually interested in this, at least enough to open
a new thread on it?
Dave Storrs
On Tue, 5 Dec 2000, Steve Fink wrote:
> David Grove wrote:
>
> > Also, as far as documentation goes, I think it _should_ be written by
> > apprentices, so that non-masters can understand it too. That's always been
>
> Except it's a particular duty that nobody really likes to perform. Which
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 Wed, 31 Jan 2001, Tim Bunce wrote:
> Since this thread is in the mood for quotes, here's one I'm fond of...
> It goes something along the lines of:
>
> Any fool can create a complicated system.
> The real skill is in making a simple one.
Ok, if we're all contributing qu
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 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, 23 Feb 2001, Nathan Wiger wrote:
> [EMAIL PROTECTED] wrote:
> >
> > But we can run an experiment. Warnings can be made default for the
> > first few releases of Perl 6 and we'll see what happens. If it looks
>
> Ummm, I'm not too sure about this. There are, actually, backwards
> com
7;)
represent( $foo, 'UTF-8D')
represent( $foo, 'UTF-16C')
represent( $foo, 'UTF-16D') ...etc
Maybe a couple of extra switchs on regexen as well, to force the matched
string (and any captured substrings) to be in a particular encoding.
Dave Storrs
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 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 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, 12 Apr 2001, Dan Sugalski wrote:
> I think Perl_ and maybe Perl__ would be fine. I'd rather Perl_ and _Perl_,
> but...
How about PerlF_ and PerlD_ (for Functions and Data)?
To also specify Exported and Private we could have PerlFE_,
PerlFP, etc.
Hey folks,
Ok, so I've picked up Dan's gauntlet on the debugging PDD. I've
got a pretty long list of things to put in it already, but if anyone would
care to send me their suggestions, I can get them integrated into the
initial draft. I probably won't have it ready by tomorrow, and I on
Apologies all...I have the document, but I'm having trouble getting it out
of my computer. I don't have Internet access yet and my floppy drive is
refusing to read. I'll see if I can get the printer hooked up tonight,
print the thing out, retype it at work tomorrow, and send it in then.
Dave
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
=head1 The Perl6 Debugger
=head2 Perl-level Debugging
=head3 Existing Functionality
The following is a list of the functionality in the existing Perl5
debugger; this functionality should, of course, be maintained for
backwards compatibility.
=over 4
=item T
Stack trace.
=item
Great, thanks very much.
Dave
On Fri, 27 Apr 2001, Jarkko Hietaniemi wrote:
> > > see it.) The debugger must be able to see two scopes at the same time:
> > > its own and the debuggee's.
> >
> > Could you expand on this?
>
> http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2001-02
On Thu, 26 Apr 2001, Jarkko Hietaniemi wrote:
>
> You list the particular commands as 'existing functionality'. I think
> this is a mistake, even if you didn't mean it that way, if it was just
> an artifact of your presentation format. I know that breaking
> debugging habits that have been i
On Fri, 27 Apr 2001, Dan Sugalski wrote:
> Thanks much for putting this together. I do appreciate it.
You are most welcome. I enjoyed it, and I'm looking forward to
updating it (though I'm hoping there will be a little more feedback,
particularly concerning the new suggestions).
>
On Wed, 25 Apr 2001, Johan Vromans wrote:
> Andy Dougherty <[EMAIL PROTECTED]> writes:
>
> > Starting with 'P' is useful so we can keep our acronyms such as PMC and
>
> PERIL (hi Tom!).
>
> -- Johan
< ACCENT=ENGLISH>
Please, can't I have just a little PERIL?
< /AC
On Tue, 1 May 2001, Dan Sugalski wrote:
> Right. What I'm thinking would be a good place to get to is a list of the
> functionality that the debugger needs to provide or have available to it
> from the interpreter, rather than the actual interface to the user. (Which
> is important, but a se
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
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
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
< 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
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 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 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 Wed, 9 May 2001, Larry Wall wrote:
> Dave Mitchell writes:
> : My thinking behind "if fails on one, avoid on all" was that if it failed
> : on at least one, then it may well fail on others that you dont have access
> : to - either now or in the future, and thus perhaps isnt as good an optimi
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
(I think I've got the attributions right.)
On Fri, 11 May 2001, Jarkko Hietaniemi wrote:
> On Fri, May 11, 2001 at 05:02:39PM +, [EMAIL PROTECTED] wrote:
> > Nathan Torkington <[EMAIL PROTECTED]> writes:
> >
> > Speaking as someone that has often had to work on C, Perl, Verilog and VHDL
>
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
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
> &
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.
On Wed, 16 May 2001, Nathan Torkington wrote:
> Dave Storrs writes:
> > < SARCASM=EXTREME>
>
> Everyone, please try to stop the downhill descent of the conversation.
> This is not just Dave, but others in the thread too.
For the record, the original post in
On Wed, 16 May 2001, Simon Cozens wrote:
> On Wed, May 16, 2001 at 11:14:57AM -0700, Dave Storrs wrote:
> > afraid of, and to express your concerns about it. However, the way that
> > you chose to do that ("Once quick and dirty dies, Perl dies.") implies
> > t
your concern is well taken, I think you are doing
yourself a disservice by using such inflammatory language...it makes me
(and probably others) focus more on your tone than on your point.
Dave Storrs
On Wed, 16 May 2001, Adam Turoff wrote:
> On Wed, May 16, 2001 at 08:57:42AM -0700, Peter Scott wrote:
> > It doesn't look to me like the amount of Perl one needs to know to achieve
> > a given level of productivity is increasing in volume or complexity at
> > all. What it looks like to me i
Hmmm...ok, on thinking about it, I generally agree with you.
There is only one point that I would debate (and, as you'll see, there's
a solution for that one, too):
On Wed, 16 May 2001, Nathan Torkington wrote:
> Dave Storrs writes:
> > 1) One of the great s
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.
>
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 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 Tue, 5 Jun 2001, Hugo wrote:
> I'd also like to see a specification for indentation when breaking long
> lines.
Fwiw, the style that I prefer is:
someFunc( really_long_param_1,
(long_parm2 || parm3),
really_long_other_param
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, 5 Jun 2001, Dave Mitchell wrote:
> dispatch loop. I'd much rather have a 'regex start' opcode which
> calls a separate dispath loop function, and which then interprets any
> further ops in the bytestream as regex ops. That way we double the number
> of 8-bit ops, and can have all the re
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 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 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 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 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
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 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, 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
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
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
=head1 TITLE
API for the Perl 6 debugger.
=head1 VERSION
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 HI
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
How would this handle code and/or packages that are generated at run
time? Or would that be another caveat?
Dave
On Fri, 31 Aug 2001, Steve Simmons wrote:
> > Perl6 should ship with a simple utility that shows all modules a program
> > uses, and all modules those modules use.
>
> Presumably
=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
putting
things in just because they are "trivial to code" when we don't have a use
for them.
In general, I would like to see the policy be "unless there is a
clear and demonstrated need, we don't do it." Let's just make the engine
easy enough to change that, as we discover things we didn't know we
needed, we can go back and add them in later.
Dave Storrs
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
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 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_?
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 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
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\:
e. Why is
this replacement necessary...isn't it sufficient to simply define it as
whitespace, as was done above?
Dave Storrs
On Sat, 3 Aug 2002, Ken Fox wrote:
> Dave Storrs wrote:
> > why didn't you have to write:
> >
> >rule ugly_c_comment {
> >
> /
> >
> \/ \* [ .*? ? ]*? \* \/
> >
> { let $0 := " " }
>
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
>
e of 8, but $a = $a + 3 leaves it with a
value of 9.
Dave Storrs
or hairy fishnuts" reference in
here somewhere, but I can't quite make it work.
Dave Storrs
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
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 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
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);
> }
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
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 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, 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
Is anyone else getting all the traffic from this list twice? I don't get it from any
of the other p6 lists, so I'm not quite sure what's up.
--Dks
[examples of how to create the glossary links snipped]
Assuming that we do go with the "maintain a unique list of keys in %glossary, then do
an s///" approach, I'd be willing to maintain the list of terms.
--Dks
1 - 100 of 203 matches
Mail list logo
