ions to the language in a subsequent
revision. See section 8.1 of The AWK Programming Language for more details.
For that reason alone (future-proofing the grammar), I would be leery of
going down this route.
David
Given that Perl 6 won't support an actual do-while loop a la C++ (and
yes, I know that Perl5 didn't either), how would you accomplish that?
That is, I'd like to have a loop that runs once, then checks its
condition to see if it should repeat and continues to repeat as long
as the condition is true.
On Wed, Feb 09, 2005 at 05:13:56AM -0600, Rod Adams wrote:
>
> Does
>
> ($k, $v) <== pop %hash;
> or
> ($k, $v) <== %hash.pop;
>
> make sense to anyone except me?
It's clear to me.
The only thing is that, right off the top of my head, I can't see
where it would be used. Since the order in whi
On Thu, Feb 10, 2005 at 09:45:59AM -0800, Larry Wall wrote:
> That's spelled
>
> loop {
> $foo = readline;
> ...do stuff with $foo...
> } while ( $foo );
>
> these days.
>
> Larry
Cool, perfect. Thanks.
--Dks
--
[EMAIL PROTECTED]
On Fri, Feb 11, 2005 at 05:33:29PM -0800, Ashley Winters wrote:
> On Thu, 10 Feb 2005 08:59:04 -0800, David Storrs <[EMAIL PROTECTED]> wrote:
> > On Wed, Feb 09, 2005 at 05:13:56AM -0600, Rod Adams wrote:
> > >
> > > ($k, $v) <== pop %hash;
> > > mak
On Sat, Feb 12, 2005 at 06:39:01PM +1100, Damian Conway wrote:
> pick - select at random from a list, array, or hash
OOC, will there be a way to control where C gets its randomness
from? (e.g. perl's builtin PRNG, /dev/random, egd, etc)
--Dks
--
[EMAIL PROTECTED]
On Mon, Feb 14, 2005 at 10:43:21AM +1100, Damian Conway wrote:
> David Storrs OOC'd:
>
> >OOC, will there be a way to control where C gets its randomness
> >from? (e.g. perl's builtin PRNG, /dev/random, egd, etc)
>
> Sure:
>
> # Use RBR (Really Bad R
On Feb 13, 2005, at 3:54 PM, David Storrs wrote:
Ok, so it requires actually overriding the rand function and providing
your own implementation. I was hoping for something a bit more
automagical (probably involving a property or role, since they seem to
be the answer to everything these days
http://www.jr.co.il/humor/noah4.txt
:-)
Regards,
David
On Tue, Feb 15, 2005 at 11:06:51AM -0800, Larry Wall wrote:
>
> But what y'all are talking about above is the other end--the return
> type. And maybe we need to enforce a newbie-friendly invariant on that
> end as well. I suppose we could default to not accepting junctional
> return values by de
On Feb 15, 2005, at 11:16 PM, Larry Wall wrote:
I admit that calling the .brainf*ck method is problematic several
ways...
And what of .c#?
Regards,
David
design of the Perl 6 language. Unfortunately an implementation does
> not yet exist, but we're working on it.
Well, Autrijus is working on it :-)
--
David Cantrell | Hero of the Information Age
It doesn't matter to me if someone else's computer is faster because
I know m
st") >>.) It's just a bit of
orthogonality that allows you to give "eggs, bacon, and toast" a name
and use it later.
Junctions are "grocery lists", then.
Regards,
David
On Mon, Feb 21, 2005 at 11:01:45AM -0800, Larry Wall wrote:
>
> But rather than that, I suspect we'll see more use of constructs
> where the object to be mutated ends up being the topic, as in:
>
> some_complicated_lvalue() but= { .sortmyway(foo($_),bar($_)) }
>
> which would presumably do t
On Thu, Mar 03, 2005 at 04:09:26PM -0800, Larry Wall wrote:
> On Thu, Mar 03, 2005 at 12:36:00PM -0800, Brian Ingerson wrote:
>
> : Thanks for the mind expanding reply.
>
> You're welcome. Next time don't eat blue sugar cubes from my frig. :-)
"I know what you're thinking. 'Why, oh why, didn'
On Sun, Mar 06, 2005 at 11:58:43PM -0800, Larry Wall wrote:
> On Sun, Mar 06, 2005 at 02:13:09AM -0700, Luke Palmer wrote:
> : What is output:
> :
> : sub foo($x, ?$y, [EMAIL PROTECTED]) {
> : say "x = $x; y = $y; z = @z[]";
> : }
> :
> : my @a = (1,2,3);
> : foo($x, @a);
On Sun, Mar 06, 2005 at 04:57:38PM +0100, Leopold Toetsch wrote:
> On behalf of the Parrot team I'm proud to announce the release of
> Parrot 0.1.2.
First: Congratulations to everyone for this release!
Second: What will it take before Parrot moves to a 0.2 (0.3, 0.4...)
release?
--Dks
On Mon, Mar 07, 2005 at 03:43:19PM +0100, Aldo Calpini wrote:
> don't know if it helps, but I guess that you can also write it like
> this, if you prefer:
>
> sub greeting(Str $person) {
> returns Str;
> is export;
> "Hello, $person";
> }
>
> (this guess is based
On Mon, Mar 07, 2005 at 05:36:08PM +0100, Aldo Calpini wrote:
> David Storrs wrote:
> >Urk. I, for one, will definitely find this surprising. I would have
> >expected:
> >
> > x = ; $y = 1; z = 2 3
>
> to obtain what you have expected, you need to explicitl
On Mon, Mar 07, 2005 at 04:58:29PM -0800, Larry Wall wrote:
>
> In fact, we really haven't specified what happens when you say
>
> my Int @a is shape(3) := [1,2];
> my Int @b is shape(3) := [1,2,3,4];
>
[...]
> But I also have this nagging feeling that the user wouldn't have
> specified
On Mon, Mar 07, 2005 at 05:15:14PM -0800, Larry Wall wrote:
> On Mon, Mar 07, 2005 at 02:20:47PM -0800, David Storrs wrote:
> : Yes, I know. That's what I meant by "...arrays are objects...(sort
>
> No, they're real objects. (Though it's .elems rather than .lengt
On Mon, Mar 07, 2005 at 07:50:47PM -0800, Larry Wall wrote:
> On Mon, Mar 07, 2005 at 05:37:53PM -0800, David Storrs wrote:
> : On Mon, Mar 07, 2005 at 04:58:29PM -0800, Larry Wall wrote:
> : Is
> : there is then any way to explicitly leave off an element. Can I do
> : this:
>
Is there a way to find the name of &?SUB ? It would be useful for
error-logging and -reporting.
--Dks
On Tue, Mar 08, 2005 at 10:29:30PM -0800, Darren Duncan wrote:
> [...]
>
> By using subtypes in this way, I could remove a lot of explicit input
> checking code from my methods, which is great. Also, the "where
> clause" is not being repeated for every argument or attribute or
> variable decla
On Wed, Mar 09, 2005 at 03:38:52PM -0600, Rod Adams wrote:
> There lingers the case of:
>
>use Foo; # from above, exports &bar is MMD::Random
>
>multi sub bar {...}
>
> Does this generate an error, since one could expect this particular &bar
> to be Manhattan? Or does it assume Rando
> At 17:53 +0100 3/10/05, Thomas Sandlaß wrote:
[request for clarification of 'covariant' and 'contravariant' usage]
> >'Co' means together like in coproduction. And 'contra' is the opposite
> >as in counterproductive. With instanciating parametric types the question
> >arises how a subtype relatio
On Thu, Mar 10, 2005 at 02:22:20PM -0600, Rod Adams wrote:
> David Storrs wrote:
> >On Wed, Mar 09, 2005 at 03:38:52PM -0600, Rod Adams wrote:
> >> use Foo; # from above, exports &bar is MMD::Random
> >> multi sub bar {...}
> >>
> >>Does th
On Sat, Mar 12, 2005 at 09:36:24PM +0100, Juerd wrote:
> Larry Wall skribis 2005-03-12 12:26 (-0800):
> > And arguably, the current structure of join is that the delimiter is
> > the invocant, so cat should be defined as
> > ''.join(@foo)
>
> This is what Python does. It does not make any sen
On Tue, Mar 15, 2005 at 08:23:19AM -0800, Larry Wall wrote:
> On Tue, Mar 15, 2005 at 10:51:57AM +0100, Juerd wrote:
> : Autrijus suggested "indeed" or "id", of which I like "indeed" better,
> : because I'd like to continue using "id" with databases.
>
> "id" is too heavily overloaded with identif
On Wed, Mar 16, 2005 at 12:00:28PM -0500, Aaron Sherman wrote:
>
> The one obvious thing to POD users is the replacement of <> with [] or
> {}. Why is this? Because < and > are used in un-balanced ways in a large
> number of situations, so they should not be the primary bracketing
> constructs.
On Wed, Mar 16, 2005 at 01:30:04PM -0500, Aaron Sherman wrote:
> On Wed, 2005-03-16 at 12:25, David Storrs wrote:
>
> > I quite like <> as the bracketing characters. They are
> > visually distinctive, they connect well with their adjacent C/X/L/etc
> > without visua
On Thu, Mar 17, 2005 at 05:04:53PM -0500, Aaron Sherman wrote:
> On Thu, 2005-03-17 at 12:28, Brian Ingerson wrote:
>
> > The interesting thing to me is that all 3 syntaxes map over the same
> > data model and thus are easily interchangable.
>
> It is, however, contrary to the spirit of POD for
On Sat, Mar 26, 2005 at 10:13:54AM -0800, Larry Wall wrote:
> The thing is that these MAD props are hung on whatever node is handy
> at the time, [...]. That's the main reason for the first pass of
> translator, to reattach the madprops at a more appropriate place in
> the tree.
>
[...]
> But wit
On Fri, Apr 08, 2005 at 05:03:11PM +0300, wolverian wrote:
Hi wolverian,
> one day a friend asked if Perl 5 had a REPL facility.
> (Read-Eval-Print-Loop). I told him it has perl -de0, which is different
> [...]
> In Perl 6, the generic solution to fix this (if one wants to fix it)
> seems, to me,
"we've already been through the whole C thing and how no one uses
it"
What's the word. Will there be something like "use English"?
Regards to all,
David
ility* of using non-ascii letters in
> > identifiers, even.
> I think we already have Latin-1 in identifiers...
more's the pity.
> Let's see about UTF-8
> pugs> my $??? = 1;
> undef
> pugs> $???;
> 1
I see a sequence of
Urdu, right up to the moment that
they want their English, or Russian, or German, or Japanese users to
submit patches.
--
David Cantrell | London Perl Mongers Deputy Chief Heretic
It's my experience that neither users nor customers can articulate
what it is they want, nor can they evaluate it when they see it
-- Alan Cooper
cted:
(1..5) >>+<< ($a-$b) # list context for the expression? Promotes like
what?
(1..5) >>+<< +($a-$b) # forced scalar context -- promotes like
documented.
(1..5) >>+<< (1) # promotes like what?
Thoughts?
David Christensen
On Wed, Apr 13, 2005 at 03:50:38AM +0800, Autrijus Tang wrote:
> I am delighted to report that the first major milestone of Pugs, version
> 6.2.0, has been released to CPAN:
Autrijus and everyone else who has been working on Pugs,
As someone who has been following the Perl6 lists for years, I'd l
o repeat a letter in a character class, well, I guess it isn't. But
the first person to write <[a...]> gets what's comin' to 'em.
Regards,
David
--
David Wheeler
President, Kineticode, Inc.
http://www.kineticode.com/
Kineticode. Setting knowledge in motion.[sm]
till
getting up to speed with a lot of the P6 specific issues).
Again, apologies if this is a closed domain/already has some other
method of retrieving the same information.
Thanks,
David Christensen
I definitely like the hyper stuff how it is; maybe the answer is to
just define an infix:<[[]]> operator which returns the crosswise slice
of a nested list of lists. In any case it could be shunted aside to
some package and certainly does not need to be in core.
David
my @transposed = @
quot;;
$u = @ar[$j]; # 2|3|4
$v = %hash{$k}; # 1|7
Does this make sense to others?
David
3|4;
my $k=$j :except(2); # 1|3|4
Let me know if I'm totally abusing junctions here...
David
I image we've all written logging code that looks something like this
(Perl5 syntax):
sub foo {
my ($x,$y) = @_;
note("Entering frobnitz(). params: '$x', '$y'");
...
}
This, of course, throws an 'uninitialized value in concatenation or
string' warning when your test suite
On Mon, Apr 25, 2005 at 05:18:11AM -0600, Luke Palmer wrote:
> David Storrs writes:
> > sub foo {
> > my ($x,$y) = @_;
> > note("Entering frobnitz(). params: '$x', '$y'");
> > ...
> > }
> > This, of
t; ones, or to all traits?
4) Which of the closure traits are supported as "will" predicates on
variables? Not all of the closure traits make sense on the
variable-level -- this information will be useful when trying to parse
the "will" predicates.
Thanks,
David Christensen
On Thu, Apr 28, 2005 at 03:28:41PM +0200, Ingo Blechschmidt wrote:
> so we had junctions of Code references some days ago, what's with
> junctions of Class and Role objects? :)
Could we see some code that shows why this is a good idea? My initial
reaction is horror; I can very easily see huge n
On Sat, Apr 30, 2005 at 09:13:26AM -0500, Abhijit Mahabal wrote:
> On Fri, 29 Apr 2005, Brent 'Dax' Royal-Gordon wrote:
>
> >David Storrs <[EMAIL PROTECTED]> wrote:
> >>Could we see some code that shows why this is a good idea? My initial
> >>
On Mon, May 02, 2005 at 06:49:10PM +0200, Thomas Sandlaß wrote:
> David Storrs wrote:
> >Let's move this away from simple types like Str and Int for a moment.
>
> If you consider them simple...
When compared to
"arbitrary-class-that-was-defined-by-
On May 3, 2005, at 00:04 , Luke Palmer wrote:
I agree with you there. $Larry has said that he wants `when` to work
Shouldn't that be @Larry[0]?
Cheers,
David
smime.p7s
Description: S/MIME cryptographic signature
Is there no more
say "Two" if /hello/;
?
Regards,
David
smime.p7s
Description: S/MIME cryptographic signature
y "Two" :: leave;
infix:(/hello/, { say "Two" })
continue unless /hello/; say "Two";
/hello { say "Two" }/;
s/hello/{ say "Two" }$0/;
({}, { say "Two" })[?/hello/]();
and probably a few more I can't think of off th
ix, etc, roles defined so you can ask
for
them?
Ask for them for what?
Regards,
David
smime.p7s
Description: S/MIME cryptographic signature
On May 4, 2005, at 2:38 PM, Thomas Sandlaß wrote:
Aaron Sherman wrote:
If we agree that the first say should print 7, then we must conclude
that either we've changed the value of undef to 7, or we've created a
circular reference.
In my view of refs 7 is printed, indeed. But I've difficulty to
unde
Jonathan Worthington wrote:
"Juerd" <[EMAIL PROTECTED]> wrote:
You both use "iff". What does that mean?
I believe it's to be read "if and only if".
Yes, but that doesn't explain what it means. Rather than me try to
explain it (poorly)...
http://en.wikipedia.org/wiki/If_and_only_if
David
On May 12, 2005, at 11:59 AM, Autrijus Tang wrote:
On Thu, May 12, 2005 at 04:53:06PM +0200, "TSa (Thomas Sandlaï)"
wrote:
Autrijus Tang wrote:
pugs> split /(..)*/, 1234567890
('', '12', '34', '56', '78', '90')
Is this sane?
Why the empty string match at the start?
I don't know, I didn't in
On May 19, 2005, at 10:56 PM, Luke Palmer wrote:
In general, you should probably be declaring your parameters
with uppercase types, [...]
Luke
If so, wouldn't it make sense that 'int' is the boxed type (one less
keystroke) and 'Int' is the special case? Optimize for the common
case, an
On May 31, 2005, at 9:51 AM, Rob Kinyon wrote:
On 5/31/05, Nathan Gray <[EMAIL PROTECTED]> wrote:
As I am interested in human-readable dates and times, and having
found
no conclusive discussion on time formatting, I make my recommendation
for a syntax (to start discussion, and allow for dat
On May 31, 2005, at 1:16 PM, Rob Kinyon wrote:
What's wrong with porting DateTime?
It's back to the old question of "what's in core?" Are dates and
times something that are used in such a large proportion of programs
that they deserve to be shipped in the basic grammar? Or perhaps in
the b
On May 31, 2005, at 2:22 PM, Rob Kinyon wrote:
my ($launch_date = now() + 6 weeks) but time(9am);
Sure. $launch_date is of type DateTime. It will numify to the
seconds-since-the-epoch, stringify to some date string, and provide
all the neat-o-keen methods you want it to have.
Works for m
On Jun 15, 2005, at 3:33 PM, Patrick R. Michaud wrote:
And here they are... this is just a draft -- feel free to flame/edit/
tear it apart liberally. These are also written assuming we don't
create a perl6-general list (but it shouldn't be hard to adapt them
should one be created).
Well, I'd
On Jun 17, 2005, at 10:42 PM, John Siracusa wrote:
But the truth is that /
really does look file-path-y to me, and just plain old ugly. I
think at
least two other people had similar reactions (Martin Kuehl and Carl
Franks).
David Storrs, reporting to show solidarity, sir(acusa)!
Maybe
On Jun 18, 2005, at 9:24 PM, Damian Conway wrote:
chromatic wrote:
I find it ugly enough that I plan to name my invocants explicitly.
...which should be construed as a *feature* of the current syntax. ;-)
Damian
In that case, why do we have this feature?
Seriously. Are default invoc
Edward Peschko wrote:
> > As to what the combined
> >
> > $bar[$foo]
> >
> > would mean: that depends on what $bar contains.
> >
> I like visual clues to tell me
> what type of variable
> something is. And I disagree strongly with trying to
> steamroller the language's
> design paper-flat as
> On Mon, May 14, 2001 at 01:25:51PM +0200, Bart Lateur wrote:
> > There must be some reason why a language like Sather isn't more popular.
> > I think that iters are part of the problem.
>
> That smacks of the Politician's Syllogism:
> Something is wrong.
> This is something.
> Theref
> On Mon, May 14, 2001 at 04:50:17PM -0400, John Porter wrote:
> > Pardon my indelicacy, but - Screw how it looks in Perl5.
>
> I'm not telling you how it *looks* in Perl 5, I'm telling you (in Perl 5
> terms) what it will *mean*.
nice save
p
> --- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > Oh, didn't Larry tell you? We're making perl's parser locale-aware so
> > it uses the local language to determine what the keywords are.
> > I thought that was in the list of things you'd need to take into
> > account when you wrote the parser...
enough in time and patience to forego poor-man's error
handling for exceptions and verbosity I'd be programming in C++ with PCRE.
David T. Grove
Blue Square Group
[EMAIL PROTECTED]
[EMAIL PROTECTED]
> David Grove writes:
> : > That's not how I see it. The filehandle is naturally true if it
> : > succeeds. It's the undef value that wants to have more information.
> : > In fact, you could view $! as a poor-man's way of extracting the error
>
Uri Guttman wrote:
> so we have to get some way to denote a list of indices as a slice and
> also support some range operation as a possible component of that list
> with the knowledge that the range arguments are also indices and not
> just integers.
>
> i don't have any syntax ideas for this at
> "Where's the likes of David Grove when you need one?"
I don't even know what you're talking about.
Leave me alone. I'm learning Python...
again.
p
> -Original Message-
> From: Vijay Singh [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, June 02, 2001 10:02 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Python...
>
>
>
> Python? Didn't know you were so into tuples...
>
> I thought your head would be turned by Ruby ;-)
It is
> Perl is far more practical than experimental.
Not at the moment. That's the problem.
(Note the subtle subject change back to its original intent.)
p
Michael G Schwern [mailto:[EMAIL PROTECTED]] wrote:
> Of course, there's problems of order of definition. What happens if
> Bar.pm is loaded before Foo? Dunno.
simple sematics can be defined. If we see a declaration:
package Foo is encapulated;
then we throw an error if the namespace, Foo,
> Previously, on St. Elsewhere...
>
> Simon(e) writes...
> > But of course, I'm sure you already know what makes
> > good language design, because otherwise you wouldn't
> > be mouthing off in here...
>
> Why is it that "Me" is *mouthing off*, but you're not? Why is that?
> What makes you so *spec
> -Original Message-
> From: Simon Cozens [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 11, 2001 3:46 AM
> To: Vijay Singh
> Cc: Me; [EMAIL PROTECTED]
> Subject: Re: Multi-dimensional arrays and relational db data
>
>
> On Sun, Jun 10, 2001 at 10:13:28PM -0800, Vijay Singh wrote:
> > Why
> From: Damian Conway [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 11, 2001 4:06 PM
> To: [EMAIL PROTECTED]
> Subject: Re: suggested properties of operator results
> I think we will see n-ary comparisons allowed in Perl 6:
>
> if ($x < $y <$z < $foo) {...
>
> but as special case syntact
> If you have not been following this thread, then maybe that is
> the reason for
> the confused-sounding nature of your email.
>
> I would say Simon was the one "ignoring an issue and attacking a
> person", not
> Vijay. I think Vijay was the one pointing out that this person ("Me") was
> contrib
> On Mon, Jun 11, 2001 at 05:19:26PM -0700, Daniel S. Wilkerson wrote:
> > I would say Simon was the one "ignoring an issue and attacking
> a person", not
> > Vijay.
>
> You are wrong. Go back through the archives. Vijay has posted four
> messages: two of which are critical of Perl, two of which a
> -Original Message-
> From: Bart Lateur [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 12, 2001 10:48 AM
> To: Perl 6 Language Mailing List
> Subject: Re: Social Reform
>
>
> On Tue, 12 Jun 2001 08:54:13 +0100, Simon Cozens wrote:
>
> >On Mon, Jun 11, 2001 at 05:19:26PM -0700, Daniel S.
> > Well, I *have* been following the discussion. And to me, it looks indeed
> > like you, Simon, were indeed attacking ME on non-technical grounds.
> > Vijay just jumped in for him, like a lioness trying to protect her
> > kittens.
>
> Which he does from time to time, as do most of us, myself lik
> On Thu, Jun 21, 2001 at 10:31:22PM +0100, Graham Barr wrote:
> > We can have a huge thread, just like before, but until we see any kind
> > of update from Larry as to if he has changed his mind it is all a bit
> > pointless.
>
> For what it's worth, I like it.
>
> > > Does anyone else see a prob
When you blass an object in Perl, you give it exactly
one type. The @ISA variable allows that type to refer
to many other classes as the inheritance tree. @ISA
is a list, but ref($obj) isn't. This means that you
sometimes have to create a lot of useless classes to
work around this limitation.
A s
Peter Scott wrote:
> What's wrong with multiple inheritance?
You have to create a whole load of extra classes whose only
purpose is to define a list of superclasses. Compare:
bless $self, qw(Employed Male);
with
package Employed_Male;
@ISA=qw(Employed Male); # multiple inheritance
...
David L. Nicol wrote:
>
> > The other standard solution is to
> > add a "Person has-a Employment_Status" relationship,
> > but that doesn't feel much better.
>
> It feels fine to me. Person has-a gender, person has-a job,
> it's more politi
Mark J. Reed wrote:
> Okay, but now we're getting into the fundamental O-O model for
> Perl. I guess that's fair game? You can certainly make the case
> that prototype-based inheritance makes at least as much sense
> as class-based inheritance for a dynamic language like Perl.
> But that's a maj
Michael G Schwern wrote:
> Rather than stumbling around in the dark here, is anyone actually
> experienced with object inheritance? Any Self programmers out there?
> Someone that's actually used this technique often and understands what
> works and what does? Any books/articles to recommend?
I
Oh boo hoo. Might I suggest a good introductory Perl book?
p
On Saturday 28 July 2001 12:32, raptor wrote:
> I've/m never used/ing "elseif" ( i hate it :") from the time I have to
> edit a perl script of other person that had 25 pages non-stop if-elsif
> sequence) ... never mind there is two c
This makes no sense. ?: tests a boolean value, which is either true or false.
There is no ternary state for a boolean value. True/False, Yes/No, On/Off,
1/0. Are you suggesting Yes/No/Maybe? Or are you redefining True and False?
Doesn't matter. What you're asking has no counterpart in boolean l
> I think they're supposed to be both by perl thingie and by value. So:
>
>my $foo is const = 0 is true;
>
> $foo has the property const, while the value 0 in $foo has
> the property true.
So, if I do
my $foo is constant = new Counter(0);
$foo->increment # OK
my $bar = new Counter(0) is
> They list two reasons to make your class final. One is security
> (which might actually be valid, but I doubt it will hold up to
> determined attack), the other though...
>
> You may also wish to declare a class as final for object-oriented
> design reasons. You may think that your cla
David L. Nicol wrote:
> How about some nice introductory links for MOP theory? The
> above-linked post is also the only time I recall seeing aspect
> theory mentioned in here either. Someone explained aspectJ to
> me at a PM meeting and it sounded like a sure recipe for
> comple
Uri Guttman
> we are planning automatic over/underflow to bigfloat. so there is no
> need for traps. they could be provided at the time of the
> conversion to big*.
OK. But will Perl support signaling and non-signaling NANs?
Dan Sugalski wrote:
> Okay, I'm whipping together the "fancy math" section of the
> interpreter assembly language. I've got:
[...]
> Can anyone think of things I've forgotten? It's been a while
> since I've done numeric work.
I'm not sure where this belongs, but I'd really like to have
a usage
I think this is one of many steps in the right direction. Actually, I have a
class item defined in my fork as:
class foo
reserve bar scalar;
member bar {
default(bar) = '1';
set(bar) = {some code};
get(bar) = {some code};
ensure(bar) = {some code};
confirm(bar) = {some co
Brent Dax wrote:
> And I didn't see anything about you being able to hyper =,
> so ^= ought to be alright too.
I would expect
@a ^= 1; # sets default value for (all elems of) @a
@a ^+= 1; # increments each element of @a
etc.
Dave.
--
Dave Whipp, Senior Verification Engineer,
Herein are drafty grumblings.
Part of quitting smoking is that my hubris has gone back up.
Here are critical first-impression notes on Apo3. Praise has
been eliminated to save space.
http://www.perl.com/pub/a/2001/10/02/apocalypse3.html?page=1
> Operator precedence should be as simple
Michael G Schwern wrote:
> Binary ;
>
> This worries me. Giving ; two meanings makes basic language parsing
> harder, which would be fine if there was a big payoff, but there's
> not. Just making shorthand for [[1,2,3],[4,5,6]] doesn't seem worth
> it. What am I missing here?
What you migh
Damian Conway wrote:
> David Nicol wrote:
>> Hear ye, hear ye, Ming of Mongo has declared!
>
> I really hope I'm just missing the implicit smiley there.
What you're missing is me wracking my memory to remember what
Dr. Zharkov called his tunneling craft that
401 - 500 of 1041 matches
Mail list logo
