Hello all.
I'm here mostly as a lurker to keep up with the evolving structure of
p6, but will try to contribute something useful when I can.
Good to be aboard.
Paul
__
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 5:02 AM +1300 3/6/03, Sam Vilain wrote:
> > *{$_} = \&{"Class::$_"} foreach (qw(method method2 method3));
> > Gives you everything that inheriting a class does, apart from the
> > ->isa() relationship. And potential unwanted namespace pollution.
>
ate methods if we can help it.
I think I need an exampleunfortunately I'm at work and haven't the
time to properly peruse the one you offered. Thus I must apologize, and
wait for more input.
Paul
__
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/
--- [EMAIL PROTECTED] wrote:
> > Are you speaking in terms of limitation, or requirement?
> > It would be nice to have a syntax solution. I've seen p5 interfaces
> > with stubs that die so that you have to override them in a
> > subclass. It works, but seems a little kludgy.
>
> Back in 1988 prog
> > And I'm coming in late on this. Are you saying you want
> > Exporter/%EXPORT_TAGS functionality built into the language and
> > into all objects? Wouldn't that jack up the overhead?
>
> No. All I'm saying is that this sort of construct:
>
>*{$_} = \&{"Class::$_"} foreach (qw(method metho
--- Andy Wardley <[EMAIL PROTECTED]> wrote:
> Associations *are* fundamental things, but I don't think they are
> part of an object. They describe relationships between objects and
> should exist independantly and orthogonal to them.
Agreed. Is there any reason that shouldb't be done with somet
> I made a mistake in my original post, they definitely need to be
> left-associative. Your example should obviously be interpreted as:
>
> (.method given $x) given $y; # calls $x.method
ok.
> I think this is similar to how I mentioned that a duplicate 'for' is
> pointless. Just because poi
Just in case anyone cares, page 6 is requiring that I scroll
horizontally. I'll live, but if it can be easily fixed, that's a Good
Thing. :)
Haven't read the rest yet -- still working on it.
Paul
--- Damian Conway <[EMAIL PROTECTED]> wrote:
> Like the fully-laden
t;
> $x and $y $y if $x
> $x or $y$y unless $x
> $x . $y $y <~ $x
> $x ( $y ) $y ~> $x
I have no idea what you mean by this.
Paul
__
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/
--- Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Piers Cawley wrote:
> > Coroutines end and DFG
> > Nobody explained what DFG stands for.
>
> It's a commonly used TLA standing for Data Flow Graph, which
> accompanies the CFG (Control Flow Graph). Both are necessary
> for register allocation
--- Brent Dax <[EMAIL PROTECTED]> wrote:
> method x ($me: $req, ?$opt, +$namedop, *%named, [EMAIL PROTECTED]) { ... }
>
> Yikes. And I thought we were trying to get *away* from line noise?
>
> Seriously, can't we use something rather prettier, like this?
>
> method x($me: $req, $o
> The problem is that if you have multiple optional or named
> parameters, things start getting uncomfortably prolix, and default
> values end up a long way from their owners:
>
> multi substr(Str $str, $from is optional = $CALLER::_,
> $len is optional = Inf, $new is optional) {...
So now putting C-style comments in p6 should be about as easy as
macro circumfix:/*...*/ () is parsed(/.*?/) { "" }
That's so easy I might even *use* it, lol
Not that I've ever really felt the need with # and =doc/=cut.
But just to make sure I'm getting it:
macro circumfix:... () is pa
> I don't know that that means we couldn't have an C
> spelling, though. And C (or something easier to spell)
> for the * case. If we have C and C, I think
> it would be appropriate to have names for the other linenoise as
well.
I'd say "please".
> (Percentage of me that really cares: 20%.
I apologize for not including a previous message thread -- I
fumble-fingered myself out of all the relevant ones
Still, I'd just like to cast my tiny vote regarding inferences.
I'd like to be able to write classes that can take advantage of
screaming speed, and types contribute.
I'd like to
> The sugar I'm using here is to go from
>
>$db.do_sql("select * from Foo");
> to
>$db.select * from Foo;
Since we're fishing, call it a circumfix operator, something like
sql...execute.
Like this:
$db.sql select * from Foo;
execute;
_
> I don't see a problem. Scalar == Int|Num|Str|Ref, so
> Scalar.isa("Int").
Scalar.isa("Int") && Int.isa("Scalar")
__
Do you Yahoo!?
Yahoo! Web Hosting - establish your business online
http://webhosting.yahoo.com
> > Doesn't C give you this?
>
> Not really. A variable declared with can be accessed from
> anywhere in the program, just by redeclaring it or calling it with
> the "package::" syntax.A variable declared with can be
> accessed outside its scope only if the user returns a reference
> to i
ould be helpful if I set up a web page where the team could give me
some alternatives to post, and folk could submit their preferences.
I suspect that there are already plenty of ways to do that, and that my
offer is weak, lol Personally, I prefer just hashing it out in the
list. But it was a
> $a ??= $b :: $c;
Are you serious?
That's completely unnecessary, but so is
$a ||= 1;
I *LIKE* it!!! =o)
__
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com
> sub foo() {
> env $s ??= 0;
> $s ++ ;
> }
Although I still prefer calling it a trait on the data, I must admit
that I like "env"...perhaps even better than "is retained".
Well, maybe not. But it's a cool thought that it's the "environment".
__
tend to use esoteric language attributes rather often
(which is not a boast -- it's a rather bad habit, but there it is).
Anyway, I like writing functions and methods that DWIM, but sometimes
WIM takes some doing. I'd rather have a name that means something to
me, too though to b
--- Miko O'Sullivan <[EMAIL PROTECTED]> wrote:
> On Thu, 20 Mar 2003, David Storrs wrote:
> > Folks, give us your address (or a PO box, or something), where we
> > can send checks. The checks won't be tax deductible, but are we
> > really doing this for the tax deduction?
>
> ... or a PayPal acc
y feel free to email me
off-list if it's more appropriate. ;o]
Paul
__
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com
> > sub myprint(+$file is IO:File is rw ::= IO:STDOUT, [EMAIL PROTECTED]) {...}
> As a side note... that sig will not do the behavior you've described.
> You instead want this:
> > sub myprint([EMAIL PROTECTED], +$file is IO:File is rw ::= IO:STDOUT) {...}
> The named parameter +$file has to go beh
--- Damian Conway <[EMAIL PROTECTED]> wrote:
> However I still think we're probably multiplying entities
> unnecessarily.
A beautiful if somewhat understated reference to Occam's Razor.
While the synoptic synthesis of the writing of William of Occam is
often translated into English as "One should
> sub foo($x ~= "foo") {...} # Append "foo" to whatever $x given
Oops. :)
That should be
> sub foo($x .= "foo") {...} # Append "foo" to whatever $x given
> sub foo($x ~= "foo") {...} # smart-test $x against "foo"
I assume the second would provide a boolean response.
--- Austin Hastings <[EMAIL PROTECTED]> wrote:
> --- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > At 10:44 AM -0800 3/25/03, Michael Lazzaro wrote:
> > >So, is anyone working on a P6ML, and/or is there any
> > >discussion/agreement of what it would entail?
> >
> > I, for one, think it's a great i
(Note forwarded to the list as penance for my silliness. :)
> > > sub foo($x .= "foo") {...} # Append "foo" to whatever $x given
> > > sub foo($x ~= "foo") {...} # smart-test $x against "foo"
>
> Well, last time I looked (granted, it could've changed numerous times
> since then) ~ was the stri
> >> |==[*]|
> >> Sarcasmeter?
> >
> >lol -- I think my BS-o-meter just redlined, too
>
> Heh. Sorry 'bout that. Bring it to OSCON and I'll get it fixed. :)
lol -- when/where is that? (Seems all I do here is ask dumb questions).
*sigh*
>
--- Jonathan Scott Duff <[EMAIL PROTECTED]> wrote:
> On Tue, Mar 25, 2003 at 12:19:30PM -0800, Paul wrote:
> > Is there a page up anywhere that summarizes the latest
> > prognostications?
>
> Mike Lazzaro had compiled the state-of-the-ops for perl6, but I don't
&g
things. :)
And FWIW, I consider this to be a very appropriate response -- an
aside, perhaps, but hey, the reason I asked the question was because I
care what helps and hinders other folk working on the list! ;o]
Paul
__
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com
--- Jonathan Scott Duff <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 31, 2003 at 12:12:54PM -0800, Michael Lazzaro wrote:
> > Don't those return C, as opposed to the value of C<$_>?
> > I.E. wouldn't it be:
> >
> > $_ and return $_ given big_calculation();
> > -or-
> > given big_calculatio
--- David Storrs <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 19, 2003 at 12:19:20PM -0800, Michael Lazzaro wrote:
> > I think newbies are going to unquestionably try and put the
> > parameters in the same order as they expect to see the eventual
> > arguments, and be durn confused it doesn't work --
--- Austin Hastings <[EMAIL PROTECTED]> wrote:
> --- Paul <[EMAIL PROTECTED]> wrote:
> > --- Austin Hastings <[EMAIL PROTECTED]> wrote:
> > > Likewise, I could argue that it be called C<=:\> (the
> > > "disgruntled muppet" oper
Error correction:
--- Paul <[EMAIL PROTECTED]> wrote:
> > > no idea how adverbial modification would affect that. Exactly
> > > what *would* adverbial assignment be? Would
> > > $a =:\ $b
> > > be like
> > > $a = \$b
Thatv should have been
> I'm looking for a Perl6 way to say that oft-repeated, oft-chained
> two-line snippet up there without declaring the temporary variable.
> Using C or C, maybe?
I think you're going to have to have some holding space, but $_ should
do it and still avoid the predeclaration. My P6 syntax is still
--- Michael Lazzaro <[EMAIL PROTECTED]> wrote:
> Note if we are truly strict about C<==> always meaning "compare
> numerically", I imagine that the line:
>
> [EMAIL PROTECTED] == [EMAIL PROTECTED];
>
> would in fact be identical to _this_ line:
>
> @a.length == @b.length;# or whate
--- Austin Hastings <[EMAIL PROTECTED]> wrote:
> Likewise, I could argue that it be called C<=:\> (the "disgruntled
> muppet" operator?) since that reflects the "equals, under reference"
> symbology. But that's yucky.
Shouldn't that be ==:/ (maybe the "severely startled muppet" operator?
lol...)
--- Austin Hastings <[EMAIL PROTECTED]> wrote:
> Dave Whipp wrote:
> > Joe Gottman wrote:
Getting deep -- sorry. :)
> > > Alternatively, there might be a new parameter type that indicates
> > > that the parameter is not evaluated immediately:
> > >
> > > sub infix:!! ($lsh, $rhs is deferred) {.
--- "Adam D. Lopresto" <[EMAIL PROTECTED]> wrote:
> I propose that since the empty pattern is no longer legal (and
> about time), we use "|" in patterns to indicate alternation without
> preference, and "||" to indicate "try the first, then the second,
> etc".
Hmm
A neat idea, but can you el
--- mlazzaro <[EMAIL PROTECTED]> wrote:
> Austin Hastings wrote:
> > It has been pointed out once already that we already talked about
> > this, and I for one am in favor of the general version of it.
> > The original discussion posited an "adverbial comparison", viz:
> > C<$a eq:ref $b>. Which, l
--- Austin Hastings <[EMAIL PROTECTED]> wrote:
> --- Paul <[EMAIL PROTECTED]> wrote:
> > > But what to do about matrix arithmetic and other simple
> > > threadable tasks?
> > > sub m_add(@a, @b) { my @result; my $i, $j; @result = @a;
> > >
--- Larry Wall <[EMAIL PROTECTED]> wrote:
> For anything other than existential issues, I believe that
> most arguments about the future containing the words "either",
> "or", "both", or "neither" are likely to be wrong. In
> particular, human psychology is rarely about the extremes
> of binary lo
--- arcadi shehter <[EMAIL PROTECTED]> wrote:
> Larry Wall writes:
> >
> > Er, how would LEAVE detect that this was the *last* time you're
> > ever going to call this routine?
> >
> > On the other hand, if we renamed FIRST and LAST to ENTER and
> > LEAVE, then FIRST would become available
--- Luke Palmer <[EMAIL PROTECTED]> wrote:
[extremely large *SNIP*]
> Maybe the "|"/"||" distinction isn't needed, and we just need a
> declarator on rules that says they are side-effect-free, and can thus
> be optimized.
[snip]
> I like this solution better than making a new operator. In Perl
>
ffectively, it allows
> one to use
> the full power of Perl as its own, recursively applied, macro language.
>
> The Filter::Util::Call module (by Paul Marquess) provides a usable Perl
> interface to source filtering, but it is not nearly as simple as
> it could be.
>
> T
y. Just because you write Foo::bar in your module doesn't mean
> > that Perl can't know which version of Foo:: you mean.
Has anyone considered the problems associated with XS code, or whatever
its replacement is?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Thu, Feb 15, 2001 at 10:43:38AM -0300, Branden wrote:
> Paul Johnson wrote:
> >
> > Has anyone considered the problems associated with XS code, or whatever
> > its replacement is?
> >
>
> The big problem about having more than one version of a module
On Thu, Feb 15, 2001 at 02:47:55PM -0500, Steve Simmons wrote:
> Paul Johnson wrote:
>
> > Has anyone considered the problems associated with XS code, or whatever
> > its replacement is?
>
> Pardon my ignorance, but what's XS code?
perldoc perlxs
perldoc perlxstu
ings
were disabled locally using no warnings or $^W =0. This includes all
files that get included via use, require or do. Think of it as the
Perl equivalent of the ``lint'' command.
Paul
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
o globally override C warnings>...
This is what the -W command-line flag does.
> but it seems like we're right back to having to remember
> -w again.
Paul
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
On Mon, Mar 26, 2001 at 10:02:40AM -0600, David M. Lloyd wrote:
> $obj->method; # Clearly void context.
Unless it's not. For example as the last statement in a subroutine.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
gards to the
> concept of "nosideeffects".
By using a correct term, although it may be unknown to the average
programmer, the programmer is presented with an oportunity to learn, and
may even be exposed to a completely new programming paradigm.
And, by the way, it is already possible
's recent patch changes this for "do" at least.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
sation and embellishment is allowed, but don't get too far off
the beaten track or people won't be sure which message they should post
next and then the thread will die.
[ :-) for those who like such things ]
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
pretty good track record with these sorts of
things.
Anyway, what do you think this is? Some kind of democracy?
:)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
trap?), which is only
> >one byte (no args) and which breaks into a handler which can check
> >various flags and do stuff. very reminiscent of the trap op code of many
> >cpu's.
>
> Sure, we can do that too.
I think something like that will be necessary.
And ultimately it's going to be possible to directly manipulate the
optree, even while a program is running, right?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Sat, Jul 07, 2001 at 09:58:54PM -0400, Uri Guttman wrote:
> >>>>> "PJ" == Paul Johnson <[EMAIL PROTECTED]> writes:
>
> PJ> Some method of attaching a callback function to arbitrary opcodes would
> PJ> be very useful.
>
> how would y
ere they both false?
Verilog, a Hardware Description Language, is an example of a language in
which this is possible, using the VPI.
> For symmetry a begin-of-block opcode can be imagined, also, but I have
> hard time thinking what would setup the code to run in there unless we
> allow for time travel :-)
See above?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Mon, Jul 09, 2001 at 11:46:30PM -0500, Jarkko Hietaniemi wrote:
>
>
> XML
> is
> much
> too
> verbose
And it should be neither written nor read by people ;-)
> .
>
>
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
;
> > uri
>
> We must demand that the feature come with a way to seal the current
> context from manipulation, even possibly a way to block accesses.
Doesn't sound very Perlish to me.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ah. Our canon of scripture?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
w, if you were proposing that named subroutines should behave like
closures in this regard, which is what Piers and probably most others
were expecting, I suspect that you would probably get broad agreement.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Wed, Aug 22, 2001 at 10:34:49AM +0100, Dave Mitchell wrote:
> Paul Johnson <[EMAIL PROTECTED]> wrote:
> > Actually, foo() is not a closure. A closure is an anonymous subroutine
> > and foo() clearly has a name.
>
> Damain's definition of a closure inclu
ratch that example then :) But my point still stands: I
I'd actually scratch the others too. That one was probably the best :-)
> think Perl 6 should have some sort of guidelines in this area, even if
> they're only a codification of what "the majority" of Perl auth
son in the quality of the test
output. The only downside is that it is another configuration on which
I need to test before making a release.
Oh, and Test::JSON works well for me. Thanks!
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
to give combined coverage for the script
and any modules used.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ble to do that, and maybe
to declare which hash keys or array elements are valid.
Do we have that already?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
solution
such as the one you noted, where the call is conditional on some
constant which can be set to false allowing the optimiser to remove the
whole thing from the op tree.
I suppose you could consider a source filter, but I couldn't recommend
that.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
--- [EMAIL PROTECTED] wrote:
> . . .
> -Such an "eigenmethod" is delegated to C<.meta> just as method like
> . . .
> +Such an I is always delegated to C<.meta> just as
changing "eigenmethod" to I should also change "an"
to "a":
+Such a I is always delegated to C<.meta> just as
^
Small
n assist with?
As far as strategy is concerned, I think this is the right way to go. I
don't see any point in rewriting the Java code if it is doing everything
necessary (I discovered I needed a fairly recent (or possibly just not
ancient) version of java to get it to work), and being consistent with
On Mon, Apr 10, 2006 at 10:26:14AM -0700, Dan Fabulich wrote:
> Paul Johnson wrote:
>
> Re: CPAN...
> >I don't see a problem with that sort of thing going on CPAN, at least
> >not from that point of view, but I do wonder if it is worthwhile given
> >that it will
_.foo for @things_to_foo;
or something.
I like lining up my code as much as the next programmer, and probably a
lot more, but I just don't see the need for this syntax which seems
ugly, confusing and unnecessary.
But then again, as I said, I really don't see the problem that i
CHED */ to shut up lint, writing
if ((a = b)) to shut up gcc, and even adding # uncoverable to keep
Devel::Cover quiet ;-)
[ No, that last one doesn't work yet. ]
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Thu, May 04, 2006 at 01:56:44PM +0300, Markus Laire wrote:
> On 5/1/06, Paul Johnson <[EMAIL PROTECTED]> wrote:
>
> >But then again, as I said, I really don't see the problem that is being
> >solved.
>
> This "long-dot" can be used for many thin
; %foo {'bar'} >> DTRT, but I can't
> remember it", which certianly happens to me fairly often.
Well, I'd obviously quite like that ;-)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
in
any Perl 6 development, discussions, or other activities. PerlNet exists to
provide support for the Perl community, and if there's anything I can do to make
it more suitable to help the Perl 6 effort, then I'd be very happy to do my best
to make it happen.
All the very best,
dard model can
take the small overhead hit of whatever internal shenanigans they need
to implement, and just about anything like that can be stuffed into a
module now, can't it?
So the upshot is, a standardized metamodel seems like the way to go to
me
And Congrats again, gramps. May y
eed,
http://www.copyright.gov/circs/circ03.html only talks about:
The symbol © (the letter C in a circle), or the word “Copyright,” or
the abbreviation “Copr.”
I wouldn't have said anything, but your correction seems to indicate
that the (C) is important. Is my information outdated?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
eneral), you should feel very encouraged to do so, even if it's with the
intention of migrating that content in the future.
Cheerio,
Paul
--
Paul Fenwick <[EMAIL PROTECTED]> | http://perltraining.com.au/
Director of Training | Ph: +61 3 9354 6001
Perl Training Australia| Fax: +61 3 9354 2681
ion-ShareAlike license, as well as the prevailing P6/Pugs license?
Cheerio,
Paul
--
Paul Fenwick <[EMAIL PROTECTED]> | http://perltraining.com.au/
Director of Training | Ph: +61 3 9354 6001
Perl Training Australia| Fax: +61 3 9354 2681
general it is much better to ignore modules whilst gathering
coverage. This has the added bonuses of making the whole thing
quicker, using less space, and mostly working.
So something like perl -MDevel::Cover=+ignore,\\.pt$ ... might be what
you are really looking for.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
file ($db, $file, $options);
print_branches ($db, $file, $options) if $options->{show}{branch};
print_conditions ($db, $file, $options) if $options->{show}{condition};
print_subroutines($db, $file, $options) if $options->{show}{subroutine};
}
}
>From h
d add after "use
> Devel::Cover" to make it works as
> "-MDevel::Cover=+ignore,\\.pt$ ...".
I think that "use Devel::Cover qw( +ignore .pt$ );" should do that.
See -M in perldoc perlrun.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
How about one of these?
==
class Baz {
has $.a is restricted;
has $.b is controlled;
has $.c is unique;
has $.d is shared;
has $.e is queued;
has $.f is token;
...
}
--- John Drago <[EMAIL PROTECTED]> wrote:
> I asked this via the Google Groups interfa
--- John Drago <[EMAIL PROTECTED]> wrote:
> James Mastros wrote:
> > I don't like the name synchronized -- it implies that multiple
> > things are happening at the same time, as in synchronized swiming,
> > which is exactly the opposite of what should be implied.
> > "Serialized" would be a nice n
--- John Drago <[EMAIL PROTECTED]> wrote:
> > You mean "is parallel" as a synonym for "is async"?
>
> I think "is parallel" denotes something as usable by multiple threads
> simultaneously, "in parallel".
> "is serial" would denote that only one thread can use the $thing at a
> time, exclusively
--- John Drago <[EMAIL PROTECTED]> wrote:
. . .
> > class QueueRunner {
> >our sub process_queue(Code @jobs_in) {
> > my @ans is serial;
> > @ans.push map { async { &_() } } @jobs_in;
> > @ans;
> >}
> > }
> > my @answer = QueueRunner.process_job_queue( @jobs );
>
> Actual
--- Ashley Winters <[EMAIL PROTECTED]> wrote:
> On 6/2/06, Paul Hodges <[EMAIL PROTECTED]> wrote:
> >
> > my @answer = map { async { &_() } } @jobs;
>
> That still seems too explicit. I thought we had hyperoperators to
> implictly parallelize for us:
>
--- Larry Wall <[EMAIL PROTECTED]> wrote:
> On Sat, Jun 03, 2006 at 03:51:45PM -0700, Paul Hodges wrote:
> : { no threads;
> :print @_.»();
> : }
>
> It seems a bit odd to use a construct for its syntactic sugar value
> but take away its semantics...
>
>
eed to come back with a bit more
information.
Good luck.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
vel/Cover/DB/Structure.pm line 269
> =
I think so. Perhaps nothing was written to the database at all?
$ perl -MStorable -e 'retrieve "/dev/null"'
Magic number checking on storable file failed at ../../lib/Storable.pm
(autosplit into ../../lib/auto/Storable/_retrieve.al) line 331, at -e
line 1
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ge databases. The reason is that the database is
read into a perl data structure. (The "database" is really little more
than a Storable dump of a Devel::Cover::DB object.) I'm afraid that the
pragmatic approach its probably to throw RAM at the hardware.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Sat, Jun 10, 2006 at 07:54:28PM -0700, Scott Wang wrote:
> Hi Paul,
>
> Thanks a lot for your reply!
>
> After I turned off warning in all my product scripts
> and test scripts which I was running Devel::Cover on,
> 90% warning messages related B::Deparse deep recursion
e a great problem. So I am interested in what problems this
causes down the line. To stop the warning I suggest the following
options:
1. Fix Devel::Cover. Go on, please. You know you want to ;-)
2. Hack the source to disable the warning.
3. Filter the output.
4. Pretend you didn't see it.
Most people take the fourth option since it really shouldn't cause any
further problems.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Sat, Jun 10, 2006 at 08:14:09PM -0700, Scott Wang wrote:
> Hi Paul,
>
> You are right, I found a 0 size file under the
> "cover_db/structure" folder. After I removed that 0
> size file, my "cover" worked fine to merge all the
> data and generated HTML f
so back to foo("bar"). What's the default behavior? String doesn't Num,
does it? though is does convert if the value is good
Does that mean foo("123") should or should not dispatch to foo(Int)?
Or even foo(Num), for that matter Oy, I could see some headaches
around setting these rules in
', '3', [ \[ '**', '4', '2' ], 0 ] ], 0 ], '5' ],
0 ];
I apologize that the expression parsing isn't a little more abstracted for
you, but the result should be usable. Also, the parse_expr is designed for
also parsing variable names in the TT2 language, so the first portion of the
method applies variable names. The entire thing could be cut down
considerably if all you want to parse is math (no variables).
Paul Seamons
On Fri, Jul 07, 2006 at 10:26:13AM -0700, Scott Wang wrote:
> Hi Paul,
>
> Even, currently, there is no any zero size data file
> in structure folder in my regression code coverage run
> (lots of suites), I still got lots of messages like
> below:
> ---
> Corrupt
1 - 100 of 1009 matches
Mail list logo
