On 20/09/05, Luke Palmer <[EMAIL PROTECTED]> wrote:
> The basic idea is that, alongside Functor, you have a Zippable theory
> which defines:
>
> theory Zippable[::T] {
> multi zip (T[::A], T[::B] --> T[:(::A, ::B)]) {...}
> }
>
> Where that last coloney madness is a yet-to-be-prop
On Sep 12, 2005, at 3:56 PM, Nathan Gray wrote:
Yep, someone needs to make a diagram about Roles, too.
Here yah go.
http://svn.openfoundry.org/pugs/perl5/Perl6-MetaModel2.0/docs/
p6_role_model.jpg
I am planning on making Roles self-bootstrapping, so the class(Role)
will actually be the
Thomas Klausner writes:
> CPANTS is an acronym for CPAN Testing Service.
That would be better simplified to:
CPANTS is the CPAN Testing Service.
-- cos it's pretty obvious where the name comes from, and its being an
acronym is hardly the most important thing about it.
But if you really want
Some other possible problems:
1: if $condition is an expression with side-effects then your new construct has
a different meaning then the original code.
2: if the middle part does something that changes the value of the expression
$condition then the new construct again has a different meanin
On 19/09/05, Yuval Kogman <[EMAIL PROTECTED]> wrote:
> This solution lacks the elegance of the lazy loading approach, but
> has the best responsiveness. These implementations tend to be overly
> complex for what they do, and hence not worth the maintenance costs.
>
> The gain is that the user only
Hi,
The current format of the debug segment in Parrot packfiles (.pbc files), as
documented in doc/parrotbyte.pod, only allows for a single source file to be
named. This became insufficient some time ago since we had .include
directives; it also means that there's nothing sensible that pbc_me
On Tue, Sep 20, 2005 at 08:58:41PM +0200, Juerd wrote:
> Yuval Kogman skribis 2005-09-20 20:33 (+0300):
> > Today on #perl6 I complained about the fact that this is always
> > inelegant:
> > if ($condition) { pre }
> > unconditional midsection;
> > if ($condition) { post }
>
> I believ
Mark Reed skribis 2005-09-20 14:31 (-0400):
> Not necessarily. Consider this common idiom (in pseudo-perl5):
Common, but widely regarded as bad style. The solution is templating and
factoring in templates.
But disregarding that,
The trick is to not see it as "pre; midsection; post;" versus
"mid
Hi!
On Sun, Sep 18, 2005 at 08:18:17PM -0500, Andy Lester wrote:
> Can someone please write up a paragraph and a link that I can put up
> on qa.perl.org's front page?
Took me a bit longer than planned, but renovating our new appartment sucks
up a lot of time...
Anyway, I rewrote some of the p
Yuval Kogman skribis 2005-09-20 20:33 (+0300):
> Today on #perl6 I complained about the fact that this is always
> inelegant:
> if ($condition) { pre }
> unconditional midsection;
> if ($condition) { post }
I believe it's not inelegant enough to do something about.
The unconditi
TSa skribis 2005-09-20 19:06 (+0200):
> Please help me to understand how the context starts to exist.
What do you mean?
Do you want to know what things provide list context?
- hash assignment
- array assignment
- arrayref constructor []
- hashref constructor {}
- slurpy parameters
- list assignm
TSa wrote:
IIRC, $Larry has mentioned a Pipe type which to me seems to be
just the generic type where you configure the buffer/queue size.
In multi-threaded (or connected processes) applications the buffer
size needs tuning to balance responsiveness with throughput. Thus
your gather proposal cou
On Tue, Sep 20, 2005 at 14:31:07 -0400, Mark Reed wrote:
> On 2005-09-20 14:23, "Yuval Kogman" <[EMAIL PROTECTED]> wrote:
> > On Tue, Sep 20, 2005 at 18:19:42 +, [EMAIL PROTECTED] wrote:
> >>
> >> 2: if the middle part does something that changes the value of the
> >> expression $condition the
On 2005-09-20 14:23, "Yuval Kogman" <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 20, 2005 at 18:19:42 +, [EMAIL PROTECTED] wrote:
>>
>> 2: if the middle part does something that changes the value of the
>> expression $condition then the new construct again has a different meaning.
>
> Err, that'
Yuval~
On 9/20/05, Yuval Kogman <[EMAIL PROTECTED]> wrote:
> Today on #perl6 I complained about the fact that this is always
> inelegant:
>
> if ($condition) { pre }
>
> unconditional midsection;
>
> if ($condition) { post }
>
> I asked for some ideas and together with
On Tue, Sep 20, 2005 at 18:19:42 +, [EMAIL PROTECTED] wrote:
> Some other possible problems:
>
> 1: if $condition is an expression with side-effects then your new construct
> has a different meaning then the original code.
If it has side effects then I always
my $bool = test ... ;
if
--- Michael G Schwern <[EMAIL PROTECTED]> wrote:
> > 5.005 introduced qr//
> >
> > $ ~/Reference/5.005_04/bin/perl5.00504-32 -le '$r = qr/(p...)/; $^X
> =~ $r; print $1'
> > perl
>
> If you're using it for any serious amount of nesting (ie. building up
> a regex
> with a bunch of qr's) it didn't
Today on #perl6 I complained about the fact that this is always
inelegant:
if ($condition) { pre }
unconditional midsection;
if ($condition) { post }
Either you put the condition in a boolean var and check it twice, or
you use a higher order function and give it three bl
HaloO Juerd,
you wrote:
Does the type "List" exist? What is it? How does it fit in the
hierarchy?
I've put it below Sub in my type lattice. But that is not official,
of course.
In list context, comma provides list context to LHS and RHS, and those
lists together are flattened. (It's not exa
On Tue, Sep 20, 2005 at 07:50:03AM -0400, James E Keenan wrote:
> >I think you misunderstand. The problem is not using relative paths in
> >chdir.
> >The problem is that @INC contains a relative path. So if you change
> >directories, the ./blib/lib entry in @INC is no longer valid.
I forgot to
On Tue, Sep 20, 2005 at 02:52:53PM +0100, Nicholas Clark wrote:
> On Mon, Sep 19, 2005 at 09:42:52PM -0400, James E Keenan wrote:
> > (Secondary reason for tests needing 5.6: as you, Schwern, pointed out
> > several weeks back, doing without qr// is just too painful!)
>
> 5.005 introduced qr//
>
HaloO chromatic,
you wrote:
On Mon, 2005-09-19 at 13:01 +0200, TSa wrote:
Why shouldn't there be a lvalue traversal that
in the end makes
($x, $y) = \($a, $b);
actually mean
$x = \$a; $y = \$b;
Does this not go from one sequence point (evaluate the rhs sufficiently,
then perform the
HaloO,
Luke Palmer wrote:
The whole point was to deautomatize it! However, here's an
interesting solution: pairs are scanned for *syntactically* *on the
top level* of a function call (allowing named() or however we spell it
as a fallback when we want to be dynamic). However, :foo(bar) and foo
On Mon, 19 Sep 2005, Will Coleda wrote:
> Good! [inline] isn't real Tcl, it's specific to partcl.
>
> That test consists of the code:
>
> inline PASM {
>print "ok\n"
> }
>
> which should do the obvious thing. Odd that it's squawking about MMD_add.
It's very strange. It copied that snip
Hi Folks,
You may have noticed lots of RT traffic on very old and stale bugs.
What's going on is that I've foolishly volunteered to try to sweep out
and tidy up Parrot's bug tracker. Living in the tropics has taught me
the extreme importance of dealing with a bug problem before it gets out
of han
On Tue, Sep 20, 2005 at 11:00:58AM +0200, Leopold Toetsch wrote:
>
> On Sep 20, 2005, at 7:42, Joshua Hoblitt via RT wrote:
>
> >
> >Is this still an unresolved design issue or can the bug be closed?
>
> If in doubt just close such old [PATCH] tickets.
I'm just trying to be thorough. Hopefully
On Mon, Sep 19, 2005 at 11:18:17PM -1000, Joshua Hoblitt wrote:
> On Tue, Sep 20, 2005 at 12:33:38AM -0700, Brent 'Dax' Royal-Gordon wrote:
> > > > I submitted the patch below my sig way back in August 2002, in ticket
> > > > 16622. It documented the then-current naming conventions for
> > > > str
On Tue, Sep 20, 2005 at 12:33:38AM -0700, Brent 'Dax' Royal-Gordon wrote:
> > > I submitted the patch below my sig way back in August 2002, in ticket
> > > 16622. It documented the then-current naming conventions for
> > > structures. Is it still accurate and/or a good idea? Should it (or an
> >
On Mon, Sep 19, 2005 at 09:42:52PM -0400, James E Keenan wrote:
> (Secondary reason for tests needing 5.6: as you, Schwern, pointed out
> several weeks back, doing without qr// is just too painful!)
5.005 introduced qr//
$ ~/Reference/5.005_04/bin/perl5.00504-32 -le '$r = qr/(p...)/; $^X =~ $r;
Michael G Schwern wrote:
On Mon, Sep 19, 2005 at 09:42:52PM -0400, James E Keenan wrote:
Schwern: Do you think it's worthwhile accounting for this MakeMaker
anachronism in writing test files, i.e., providing an absolute path to
every chdir call?
I think you misunderstand. The problem is
On Mon, Sep 19, 2005 at 09:57:24PM -0700, Sean O'Rourke via RT wrote:
> "Joshua Hoblitt via RT" <[EMAIL PROTECTED]> writes:
> > Since the rx_* ops are on the chopping block is there any objection to
> > closing this bug?
>
> No objection from me. Actually, I'm not an active Parrot developer
> now
On Mon, 19 Sep 2005 11:33:07 +0200, David Landgren <[EMAIL PROTECTED]> wrote:
> Gábor Szabó wrote:
> > What do you think about adding a has_license kwalitee to CPANTS ?
> > Checking if the META.yml has that entry ?
>
> This will penalise all the modules that use ExtUtils::MakeMaker, which,
> las
On Sep 20, 2005, at 7:42, Joshua Hoblitt via RT wrote:
Is this still an unresolved design issue or can the bug be closed?
If in doubt just close such old [PATCH] tickets.
-J
Thx,
leo
> > I submitted the patch below my sig way back in August 2002, in ticket
> > 16622. It documented the then-current naming conventions for
> > structures. Is it still accurate and/or a good idea? Should it (or an
> > up-to-date version of it) be committed?
>
> Yet another year has rolled by. D
34 matches
Mail list logo
