In article <[EMAIL PROTECTED]>, herbert breunung
<[EMAIL PROTECTED]> wrote:
> currently just used for compile time constants like $?LINE allright so
> far so good.
> but why not use that for all constants like
>
> my $?constant = 5;
The $? is telling us where the value came from, not that it's
In article <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]> wrote:
> That's what made me come to the conclusion that it's really "The Parrot
> Foundation".
It's not The Parrot Foundation. It's that NLNet gave a very large
targeted grant for Parrot. It's a single big donation that's driving
that.
I'm wo
In article
, Conrad Schneiker
<[EMAIL PROTECTED]> wrote:
> So over the next few months, I'm planning to learn about
> fundraising, and see what I can accomplish on behalf of Perl
> 6 development. To that end, I'm soliciting:
It's not really a money problem. It's finding someone to give the money
In article <[EMAIL PROTECTED]>, Larry Wall
<[EMAIL PROTECTED]> wrote:
> :given( $foo ) {
> : when( ( scalar @array and scalar %hash ) ~~ $_) ) { ... }
> : }
> which is exactly what I would expect from Perl 5, unless when is
> really a very intelligent macro of some sort. As far
This is actually a bug from Perl 5, but Perl 5's given is supposed to
act like Perl 6's given. The long post is in use.perl:
http://use.perl.org/~brian_d_foy/journal/35682
I was playing with a when condition that used a logical operator to see
if the topic was both an element of an array and
In article <[EMAIL PROTECTED]>, Smylers
<[EMAIL PROTECTED]> wrote:
> brian d foy writes:
>
> > In article <[EMAIL PROTECTED]>, Larry Wall
> > <[EMAIL PROTECTED]> wrote:
> >
> > > On Tue, Dec 04, 2007 at 08:28:48AM -0800, brian d foy wr
In article <[EMAIL PROTECTED]>, Larry Wall
<[EMAIL PROTECTED]> wrote:
> On Tue, Dec 04, 2007 at 08:28:48AM -0800, brian d foy wrote:
> : In article <[EMAIL PROTECTED]>, Larry Wall
> : <[EMAIL PROTECTED]> wrote:
> :
> : > : Later in the "L
In article <[EMAIL PROTECTED]>, Larry Wall
<[EMAIL PROTECTED]> wrote:
> : Later in the "Literals" section of S02, there's a chart of the
> : corresponding forms for fat arrow, pair, and paren notation. It has
> :
> :a => 'foo' :a :a()
> :
> : That looks like it might mean that thes
[[ This message was both posted and mailed: see
the "To," "Cc," and "Newsgroups" headers for details. ]]
In article <[EMAIL PROTECTED]>, cdumont
<[EMAIL PROTECTED]> wrote:
> oh, it might not be relevant in many ways but :
>
> http://iamseb.com/seb/2007/12/perl-on-rails-why-the-bbc-fails-at-th
In article <[EMAIL PROTECTED]>, TSa
<[EMAIL PROTECTED]> wrote:
> The only operator that can be used to investigate these values should
> be ~~ and the given/when statement that uses it.
Why should that be true? What's wrong with treating it as an object
like anything else?
The trick is limitin
In article <[EMAIL PROTECTED]>, Darren Duncan
<[EMAIL PROTECTED]> wrote:
> At 3:20 PM -0500 10/6/07, brian d foy wrote:
> >For comparisons, how are we going to use Inf and NaN? Are those going
> >to be special flyweight objects, so:
> >
> >$x = 1 / 0;
In article <[EMAIL PROTECTED]>, Moritz Lenz
<[EMAIL PROTECTED]> wrote:
> brian d foy wrote:
> > * If I can match $x to NaN (or its stand-in), what happens when $x is
> > undef?
>
> undef is a property of the container variable (that it holds no value),
> wher
This is basically the same question I had about file test operators
earlier
(http://www.nntp.perl.org/group/perl.perl6.language/2007/04/msg27415.htm
l). I never got an answer on my syntax question and the discussion went
off to talk about file tests instead of pair notation.
>From S02 "The genera
In article <[EMAIL PROTECTED]>, brian d foy
<[EMAIL PROTECTED]> wrote:
> I'm thinking about how to explain Perl 6's numbers to the beginners
> just picking up Learning Perl 6. I had some questions about NaN and Inf
> (which I can't just try since neither P
I'm thinking about how to explain Perl 6's numbers to the beginners
just picking up Learning Perl 6. I had some questions about NaN and Inf
(which I can't just try since neither Parrot or Pugs appear to know
about these yet).
* In S02's table of "Immutable types", it mentions that Int allows Inf
is cool. Also, I do not know how periodically that
> would be, but it might be a good idea to join some of them in turns and
> ask brian d foy to publish them in TPR as well.
Yes, I'd publish them. :) However, I don't want to publish something
that's already on Perl.com.
I have a feeling we've sorta assumed some use cases for whatever Pod
design we're advocating, so I thought I'd write down what I'd like to
do with Pod. At this level, I don't care how it gets done, which model
it uses, or anything else.
This isn't a fantasy wishlist of anything I think I might wan
In article <[EMAIL PROTECTED]>, Smylers
<[EMAIL PROTECTED]> wrote:
> Juerd Waalboer writes:
>
> > Smylers skribis 2007-06-21 21:33 (+0100):
> >
> > > I disagree. perldoc.perl.org was started by JJ, gained popularity,
> > > and then got awarded the official blessing of the onion. Over the
> > >
In article
<[EMAIL PROTECTED]>, Damian
Conway <[EMAIL PROTECTED]> wrote:
> Mark Overmeer wrote:
>
> [...yet another honest and heartfelt plea for Pod 6 to be something
> entirely different from what it is currently designed to be.]
>
> The solution is simple, you know, Mark. Why not just write u
In article
<[EMAIL PROTECTED]>, Chaddaï
Fouché <[EMAIL PROTECTED]> wrote:
> The "Learning Perl 6" argument seems
> equally contrived to me since anyway you don't need POD to understand
> programming in Perl and I never actually learned POD until I wanted to
> do a real module and document my littl
In article <[EMAIL PROTECTED]>, brian d foy
<[EMAIL PROTECTED]> wrote:
> There are other things to consider, and to me it looks like this design
> decision isn't based on what's easier for the Perl 6 programmer but
> what's easier for the implementors.
My
In article <[EMAIL PROTECTED]>, Damian Conway
<[EMAIL PROTECTED]> wrote:
[writing publicly to head off any notions there's a personality problem
here]
> brian wrote:
> > I know you think it's easier to teach and explain, but that's because
> > you came up with it.
>
> I hope I'm not that shal
In article <[EMAIL PROTECTED]>, Smylers
<[EMAIL PROTECTED]> wrote:
> brian d foy writes:
>
> > In article
> > <[EMAIL PROTECTED]>, Damian
> > Conway <[EMAIL PROTECTED]> wrote:
> >
> > > No. It's Pod. *Any* line that begins wi
In article <[EMAIL PROTECTED]>, Damian Conway
<[EMAIL PROTECTED]> wrote:
[ First, I should note that whatever we end up with, that's the party
line and that's what I teach, but before we end up there, I know from
my years of experience teaching that certain sorts of questions are
going to come up.
In article
<[EMAIL PROTECTED]>, Damian
Conway <[EMAIL PROTECTED]> wrote:
> No. It's Pod. *Any* line that begins with '=begin' always starts a Pod
> block. Always.
As you know, one of the biggest complaints about Perl is that you have
to have a lot of special rules knowledge to figure some things
In article <[EMAIL PROTECTED]>, Larry Wall
<[EMAIL PROTECTED]> wrote:
> On Tue, May 01, 2007 at 10:04:50AM -0500, brian d foy wrote:
> : Is there going to be a Perl 6 equivalent to $ARGV (the current filename
> : for the ARGV filehandle)?
>
> Hmm, well, we did away
Is there going to be a Perl 6 equivalent to $ARGV (the current filename
for the ARGV filehandle)?
This is something I wanted to use in an example in the Learning Perl 6
filehandles chapter:
http://www.learningperl6.com/Chapters/11.filehandles.html
I was thinking about default filehandles yesterday. select() doesn't
seem to be around except as an "Unfiled" function in S16.
Then, as I was looking at
.say( "Hello World" );
and
$ERR.say( "Hello standard error" );
I figured this might work, and does. Topicalizing a filehandle kinda
In article
<[EMAIL PROTECTED]>, Luke
Palmer <[EMAIL PROTECTED]> wrote:
> However, now we have stat($file).size.
That's sorta fine with me. That makes it even easier to explain to
newbies, although I'd need method names for the other tests.
However, junctive tests are a mighty attractive featur
As I was playing around with dirhandles, I thought "What if..." (which
is actualy sorta fun to do in Pugs, where Perl 5 has everything
documented somewhere even if nobody has read it).
My goal is modest: explain fewer things in the Llama. If dirhandles
were like filehandles, there's a couple of pa
In article
<[EMAIL PROTECTED]>, Mark J.
Reed <[EMAIL PROTECTED]> wrote:
> I think I need to reread the docs. What's the colon in the method calls for?
>
> (That is, why is it $stat_obj.:r instead of just $stat_obj.r ?)
I can't answer the "why" question, but the stuff in S02 might help you.
Look
So far (eep!), the documentation talks about file test operators as
working with pairs, which will be a weird thing to explain, I guess.
I'm wondering if this matters to the mere user at all, and if we should
even talk about them in terms of "pairs". I don't want a different set
of terms in the doc
In article <[EMAIL PROTECTED]>, Larry Wall
<[EMAIL PROTECTED]> wrote:
> On Thu, Apr 12, 2007 at 01:52:50PM -0500, brian d foy wrote:
> : Here's my code example that motivates this question. For a Llama6
> : exercise with file test operators, I wanted to create a lit
In article <[EMAIL PROTECTED]>, Moritz Lenz
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> brian d foy wrote:
> > At the moment the file test operators that I expect to return true or
> > false do, but the true is the filename.
>
> that helps chaining of file test:
In article <[EMAIL PROTECTED]>, Moritz Lenz
<[EMAIL PROTECTED]> wrote:
> brian d foy wrote:
> > At the moment the file test operators that I expect to return true or
> > false do, but the true is the filename.
> that helps chaining of file test:
>
> $fn ~~ :
In article <[EMAIL PROTECTED]>, Brandon
S. Allbery KF8NH <[EMAIL PROTECTED]> wrote:
> File tests are supposed to return something which:
> - behaves as a Bool
> - stringifies as a filename
> - numifies as a file size or as a time, if appropriate
> - propagates a stat object (obviating perl5's mag
In article <[EMAIL PROTECTED]>, Brandon
S. Allbery KF8NH <[EMAIL PROTECTED]> wrote:
> On Apr 12, 2007, at 14:52 , brian d foy wrote:
>
> > At the moment the file test operators that I expect to return true or
> > false do, but the true is the filename. I expect
In article <[EMAIL PROTECTED]>, David Vergin <[EMAIL PROTECTED]>
wrote:
> on 4/11/2007 10:29 AM brian d foy said the following:
> > The $*ARGS variable shows up in this file, which looks like it's still
> > maintained:
> > http://svn.pugscode.org/pu
At the moment the file test operators that I expect to return true or
false do, but the true is the filename. I expected a boolean, for no
other reason than Perl 6 has them so it might as well use them. The
section on Smart Matching in S03 says that the ~~ doesn't have to
return a boolean, but asi
In article <[EMAIL PROTECTED]>, Moritz Lenz
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> brian d foy wrote:
> > Under the section "The for Statement" in S04, it says that the diamond
> > operator
> >
> >while( <> ) { ... }
> >
Randal and I are starting work on "Learning Perl 6", and now
that I've completed a lot of other things, I can actually start
paying attention to Perl 6. Here's the first of my stupid, "where
have you been for the past 2 years you moron" questions. :)
I'm working on the chapter on I/O (Chapter 5 in
41 matches
Mail list logo
