Both Luke and I missed the fact that my mail and his response went
only to each other so, with his permission, here it is as a forward.
--Dks
Begin forwarded message:
From: Luke Palmer <[EMAIL PROTECTED]>
Date: October 5, 2005 1:48:54 AM EDT
To: David Storrs <[EMAIL PROTECTED]>
Subject: Re:
Even better! I jumped the gun! Never Mind! Nothing to see Here!
Thanks again!
On Oct 4, 2005, at 10:15 PM, Will Coleda wrote:
This is *great* and I've already started converting partcl to take
advantage.
One problem I've discovered:
operators["<<"] = OPERATOR_SHL
This is probably becaus
This is *great* and I've already started converting partcl to take
advantage.
One problem I've discovered:
operators["<<"] = OPERATOR_SHL
This is probably because:
<*>"<<"{STRINGCONSTANT} {
Is too permissive. Can we perhaps just allow {ID}s ?
Thanks again! This is great! Woo!
On Oct 4,
[EMAIL PROTECTED] (Joshua Juran) writes:
[...]
> > Google for "NCI gtk". There is also a weekly summary entry but the
> > xrl.us shortcut seems to have expired.
If I found the same link you found then it's not the xrl.us shortcut -
http://xrl.us/cw78 - but the Google group link that stopped worki
When I match these rules:
p6rule(" ",
classname, "attrdef")
p6rule("\( \s* x \s* \)", classname, "parenlist")
p6rule("{ \s* y \s* }", classname, "codeblock")
against this string "(x) { y }", I get the following error:
src/inter_call.c:129: failed assertion `PObj_is_PMC_TEST(sig_p
On 10/4/05, Luke Palmer <[EMAIL PROTECTED]> wrote:
> If that ends up being common, we could create a syntax for it, like
> postfix:<...>:
>
> @array... # same as (@array, undef xx Inf)
No, no, that's a bad idea, because:
@array...# same as @array.elems..Inf
So I think I'm pr
On 10/4/05, Juerd <[EMAIL PROTECTED]> wrote:
> What should zip do given 1..3 and 1..6?
>
> (a) 1 1 2 2 3 3 4 5 6
> (b) 1 1 2 2 3 3 undef 4 undef 5 undef 6
> (c) 1 1 2 2 3 3
> (d) fail
>
> I'd want c, mostly because of code like
>
> for @foo Y 0... -> $foo, $i { ... }
>
> Pugs currently does b.
... just in case you have missed autrijus's last one [1]:
Happily, leo has become a #perl6 resident; with his help, we regained
compatibility with Parrot 0.3.0's new calling conventions, and rules
support via PGE again works. The new calling conventions are much
saner; chip/leo have done a won
Juerd wrote:
What should zip do given 1..3 and 1..6?
(a) 1 1 2 2 3 3 4 5 6
(b) 1 1 2 2 3 3 undef 4 undef 5 undef 6
(c) 1 1 2 2 3 3
(d) fail
I'd want c, mostly because of code like
for @foo Y 0... -> $foo, $i { ... }
Pugs currently does b.
I agree that C should have named options (perha
On Oct 4, 2005, at 21:44, Klaas-Jan Stol wrote:
Hi,
Currently I'm doing a course 'Software Architecture' for my Master
Computer Science. For this course, I have to write a paper on some
subject that has to do with software architecture. Therefore, I
proposed to write a paper on the archite
Perl 6 Summary for 2005-09-26 through 2005-10-02
All~
Welcome to another summary, this time a day late because I was in Philly
for Serenity. If you haven't seen Serenity yet you should stop reading
this summary and go see it. The summary will be here when you get back.
I promis
On Tue, Oct 04, 2005 at 04:15:45PM +0100, Dave Cross wrote:
> David Landgren wrote:
> >Gavin Henry wrote:
> >
> >>Dear List,
> >>
> >>In "Perl Testing - A Developers Notebook" it has a section on
> >>Test::Kwalitee.
> >>
> >>I can't find this module anywhere, nothing on the CPAN or on Google.
> >
Joshua Hoblitt via RT wrote:
[nickg - Thu Apr 14 15:12:00 2005]:
Here's another odd one, which looks const-related. Uncommenting the '+='
line causes a compile error when 'c' is subsequently used.
It looks like there is still support for .const in the lexer. Is this
still an issue?
I did t
Hi,
After a show of demand for here docs on IRC (and leo's approval), I've
now modified to lexer to support them. The syntax for introducing a
heredoc is <<"XXX", and it ends on the line containing (only) XXX. For
example:-
$ cat example.pir
.sub _main
$S0 = <<"quotage"
Blah blah
Oh happy
On Tue, Oct 04, 2005 at 06:30:05PM +0200, Leopold Toetsch wrote:
>
> There are 2 philosophies amongst people: some prefer RT, others prefer
> one document in the tree. The goal could be to auto-create BROKEN from
> RT tickets then. (I prefer one file, btw ;-)
That shouldn't be too hard with the
I don't have strong opinions about this yet, but has anyone else looked
at the Perl::Critic suite of modules on CPAN?
It occurs to me that:
a) Kwalitee metrics could quite easily be implemented as Perl::Critic
plugins.
b) The plugins that it ships with (based on Perl Best Practices) may
for
Rafael Garcia-Suarez <[EMAIL PROTECTED]> wrote:
> So, such a "sensitive" modifier could be added, but its
> precise meaning would be highly dependent on the underlying
> implementation.
Okay, but there needs to be some minimum standard for it, like "the
memory in question no longer contains its or
Hi,
Currently I'm doing a course 'Software Architecture' for my Master
Computer Science. For this course, I have to write a paper on some
subject that has to do with software architecture. Therefore, I proposed
to write a paper on the architecture of Parrot, and today I got approval
of this s
I see your point. Option b does suggest that you can read ahead in a
"blocked" list and get undef's. If I had to choose just one, I think
I'd opt for d, but having two zip's one acting like c and one like d
might be useful. Then, of course, my first thought was wrong. This one
may well be, too.
--
On Tue, Oct 04, 2005 at 09:00:15PM +0200, Juerd wrote:
> What should zip do given 1..3 and 1..6?
>
> (a) 1 1 2 2 3 3 4 5 6
> (b) 1 1 2 2 3 3 undef 4 undef 5 undef 6
> (c) 1 1 2 2 3 3
> (d) fail
>
> I'd want c, mostly because of code like
>
> for @foo Y 0... -> $foo, $i { ... }
>
> Pugs curr
Hey,
I'd just like to say that I find B a bit misleading because you couldn't
tell that the first list ended, it could just have undef's at the end. I
like a because it doesn't add any data that wasn't there, of course that
could be a reason to dislike it too. On the other hand c makes a good optio
That (b) certainly seems like the sensible option to me. My second
choice would be d.
A nice thing about c is that it leaves open the possibility of lazy
evaluation (zip as much of the lists as you can, leaving open the
possibility of picking up the process later). But I still prefer b.
Maybe ther
On 10/4/05, Juerd <[EMAIL PROTECTED]> wrote:
>
> What should zip do given 1..3 and 1..6?
>
> (a) 1 1 2 2 3 3 4 5 6
> (b) 1 1 2 2 3 3 undef 4 undef 5 undef 6
> (c) 1 1 2 2 3 3
> (d) fail
>
> I'd want c, mostly because of code like
>
> for @foo Y 0... -> $foo, $i { ... }
>
> Pugs currently does b.
What should zip do given 1..3 and 1..6?
(a) 1 1 2 2 3 3 4 5 6
(b) 1 1 2 2 3 3 undef 4 undef 5 undef 6
(c) 1 1 2 2 3 3
(d) fail
I'd want c, mostly because of code like
for @foo Y 0... -> $foo, $i { ... }
Pugs currently does b.
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://con
On Oct 4, 2005, at 19:06, Andrew Dougherty wrote:
Ok, I've finally found the cause of this one, but I don't have a
portable
patch at hand.
Buried in amongst the 6827 warnings emitted by gcc is one that actually
correctly identifies the problem:
There must be some really heavily used macros
> On Tue, 2005-10-04 at 17:41 +0200, Thomas Klausner wrote:
>
> Hi all,
>
>> In june, chromatic informed me that he planned something like
>> Test::Kwalitee. AFAIK it was/is in 'proof of concept'-stage, mostly
>> because CPANTS was a fast-moving target back then (I was rewriting stuff
>> a lot...)
On Tue, 2005-10-04 at 17:41 +0200, Thomas Klausner wrote:
Hi all,
> In june, chromatic informed me that he planned something like
> Test::Kwalitee. AFAIK it was/is in 'proof of concept'-stage, mostly
> because CPANTS was a fast-moving target back then (I was rewriting stuff
> a lot...)
Yep, I ha
On Oct 4, 2005, at 18:41, Brent 'Dax' Royal-Gordon wrote:
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
As Brent is listed as author in rx.ops I wanted to make sure, if it's
ok
to remove ops/rx.ops, src/rx.c and associated files.
See also the file DEPRECATED in parrot's root dir.
I have no p
--
Walking the road to enlightenment... I found a penguin and a camel on the
way. Fancy a [EMAIL PROTECTED] Just ask!!!
http://perlmonks.org/?node_id=386673
> Dave Cross <[EMAIL PROTECTED]> wrote:
>
>> Actually the book strongly suggests that it's a real module which runs
>> the Kwalitee ch
On Fri, 30 Sep 2005, Andy Dougherty wrote:
> On Fri, 30 Sep 2005, Leopold Toetsch via RT wrote:
>
> > Andy Dougherty (via RT) wrote:
> >
> > > With a a fresh checkout (r9274) I get a number of errors where parrot
> > > eventually
> > > gobbles up all the memory on the system. Here's the first
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> As Brent is listed as author in rx.ops I wanted to make sure, if it's ok
> to remove ops/rx.ops, src/rx.c and associated files.
>
> See also the file DEPRECATED in parrot's root dir.
I have no problem with this--the rx ops were an early experiment based
On Oct 4, 2005, at 5:05, Joshua Hoblitt wrote:
On Mon, Oct 03, 2005 at 06:17:30PM -0700, chromatic wrote:
I'll check this in in two days with regard to feedback from anyone
whose
opinion matters and what to call it and where to put it, if my initial
choice isn't perfect.
I'm wondering if
Dave Cross <[EMAIL PROTECTED]> wrote:
> Actually the book strongly suggests that it's a real module which runs
> the Kwalitee checks on your code
>
> Download and install Test::Kwalitee. Then add the following code to
> your t/ directory as kwalitee.t:
>
> #!perl
>
> ev
On Mon, 3 Oct 2005, Chromatic wrote:
> Here's (finally) a collection and summary of all of the known broken
> items in Parrot right now as a patch to create BROKEN.pod in the top
> level directory. If this isn't the right name or place to put the file,
> that's fine.
> +=item * Allow Building wi
Please note again: remove *stack call directives*
* The 4 directives and 'call' are gone. If needed use please:
.param => save
.arg => restore
.return => save
.result => restore
call => bsr
* please note that *parrot calling conventions* still work of course.
* adjust s
Dave Cross wrote:
David Landgren wrote:
Gavin Henry wrote:
Dear List,
In "Perl Testing - A Developers Notebook" it has a section on
Test::Kwalitee.
I can't find this module anywhere, nothing on the CPAN or on Google.
It would only be POD, I imagine.
Anyone know where it's hosted?
Hi!
On Tue, Oct 04, 2005 at 04:15:45PM +0100, Dave Cross wrote:
> >>Dear List,
> >>
> >>In "Perl Testing - A Developers Notebook" it has a section on
> >>Test::Kwalitee.
> ..
> Actually the book strongly suggests that it's a real module which runs
> the Kwalitee checks on your code
> ..
> That
> On Tue, Oct 04, 2005 at 04:15:45PM +0100, Dave Cross wrote:
>> David Landgren wrote:
>> >Gavin Henry wrote:
>> >
>> >>Dear List,
>> >>
>> >>In "Perl Testing - A Developers Notebook" it has a section on
>> >>Test::Kwalitee.
>> >>
>> >>I can't find this module anywhere, nothing on the CPAN or on G
> David Landgren wrote:
>> Gavin Henry wrote:
>>
>>> Dear List,
>>>
>>> In "Perl Testing - A Developers Notebook" it has a section on
>>> Test::Kwalitee.
>>>
>>> I can't find this module anywhere, nothing on the CPAN or on Google.
>>
>> It would only be POD, I imagine.
>>
>>> Anyone know where it'
David Landgren wrote:
Gavin Henry wrote:
Dear List,
In "Perl Testing - A Developers Notebook" it has a section on
Test::Kwalitee.
I can't find this module anywhere, nothing on the CPAN or on Google.
It would only be POD, I imagine.
Anyone know where it's hosted?
Kwalitee, as in cpants
Gavin Henry wrote:
Dear List,
In "Perl Testing - A Developers Notebook" it has a section on Test::Kwalitee.
I can't find this module anywhere, nothing on the CPAN or on Google.
It would only be POD, I imagine.
Anyone know where it's hosted?
Kwalitee, as in cpants.perl.org, is run by Thoma
Dear List,
In "Perl Testing - A Developers Notebook" it has a section on Test::Kwalitee.
I can't find this module anywhere, nothing on the CPAN or on Google.
Anyone know where it's hosted?
Thanks.
--
Walking the road to enlightenment... I found a penguin and a camel on the
way. Fancy a [E
On Tue, 4 Oct 2005, Rafael Garcia-Suarez wrote:
language like C. So, such a "sensitive" modifier could be added, but its
precise meaning would be highly dependent on the underlying
implementation.
It would be of interest more to a perl programmer than to a Perl
programmer. Like keys() as an l
On Oct 4, 2005, at 5:11 AM, Leopold Toetsch wrote:
On Oct 4, 2005, at 3:52, Will Coleda wrote:
On Oct 3, 2005, at 6:34 PM, Leopold Toetsch wrote:
I don't see the point. Your compiler can emit, e.g.:
"while"(test, body)
That's actually how things work right now (very similar to
On 10/4/05, jerry gay <[EMAIL PROTECTED]> wrote:
> i'll also add a statement to this effect
...to the documentation...
> , if there's not one already.
On 10/4/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> jerry gay (via RT) wrote:
>
> >
> > D:\usr\local\parrot-bug\trunk>parrot -t imcc/t/syn/clash_8.pir
> > 0 branch 2
> > 2 if I0, 17- I0=0,
>
> I see. The test doesn't initialize I0 before testing it.
>
> I think we decided tha
Jarkko Hietaniemi (via RT) wrote:
t/pmc/stringok 12/35
# Failed test (t/pmc/string.t at line 556)
# got: '0
# 1
# -1
# 128
It looks like #37338 and #37339 reveal the same, now fixed, bug as #37337.
leo
Jarkko Hietaniemi (via RT) wrote:
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #37337]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37337 >
t/op/compok 6/80
# Failed test (t/op/
Jarkko Hietaniemi (via RT) wrote:
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #37336]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37336 >
$ ./parrot t/pmc/io_1.pir
This is a TODO tes
Jarkko Hietaniemi (via RT) wrote:
cc: Info: imcc/pcc.c, line 379: In this statement, an array is being
accessed o\
utside the bounds specified for the array type. (subscrbounds)^
regs[2] = arg;^
-
nice compiler
And sure enough, regs has been declared as two-elemen
Jarkko Hietaniemi (via RT) wrote:
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #37334]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37334 >
io/io_unix.c does not compile because socklen_
jerry gay (via RT) wrote:
D:\usr\local\parrot-bug\trunk>parrot -t imcc/t/syn/clash_8.pir
0 branch 2
2 if I0, 17- I0=0,
I see. The test doesn't initialize I0 before testing it.
I think we decided that Parrot doesn't provide pre-cleared I and N
registers, therefore the test
Roger Browne wrote:
b = a + a
This will call the "__add" multi, whatever it is.
My real problem occurs in Amber's HLL code where I call functions like
"__add" directly (as part of the implementation of Amber's basic types),
Well, as said, that shouldn't be necessary. If your native types
> ... infix multi subs take an optional 3rd argument (the
> destination) and that there is no good means yet to denote :optional
> NCI arguments.
OK. It's my fault for developing against the 0.2.3 release rather than
against the svn branch.
> ... Just use:
>
>b = a + a
>
> This will call
On Oct 4, 2005, at 8:11, Joshua Hoblitt via RT wrote:
[leo - Wed Apr 13 02:18:49 2005]:
The following snippet ...
$ cat b.imc
.sub main @MAIN
.local pmc b
b = new BigInt
b = 1e10
if b > 4 goto ok
print "never\n"
end
ok:
print "ok\n"
.end
... shows that th
Brent 'Dax' Royal-Gordon wrote in perl.perl6.language :
> Basically, I'd like to be able to mark a variable as "sensitive" or
> "secret". This implies that the language should overwrite the memory
> it uses before deallocating it, and that if possible it should tell
> the virtual memory system to
On Mon, Oct 03, 2005 at 06:17:30PM -0700, chromatic wrote:
>
> I'll check this in in two days with regard to feedback from anyone whose
> opinion matters and what to call it and where to put it, if my initial
> choice isn't perfect.
I'm wondering if this wouldn't be better split up into RT ticket
# New Ticket Created by jerry gay
# Please include the string: [perl #37345]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37345 >
D:\usr\local\parrot-bug\trunk>perl t/harness imcc/t/syn/clash.t
imcc/t/syn/clashok 7/1
On Oct 3, 2005, at 21:58, Roger Browne (via RT) wrote:
Under Parrot 0.2.3 the following PIR program prints "4" as
expected:
.sub "main" @MAIN
.local pmc a, b
a = new Integer
a = 2
b = a.__add(a)
print b
print "\n"
end
.end
Under Parrot 0.3.0 the same code fails like this:
On Oct 4, 2005, at 3:52, Will Coleda wrote:
On Oct 3, 2005, at 6:34 PM, Leopold Toetsch wrote:
I don't see the point. Your compiler can emit, e.g.:
"while"(test, body)
That's actually how things work right now (very similar to the
interpreter from previous versions).
Not quite:
$
60 matches
Mail list logo
