nice work,
I think this kind of redrafting can be a good foundation for
refactoring ... though I would go further and suggest an xml based
format ... if u have a .odt you can convert this to docbook ;)
one nit pick; drop 'rigorous' in title
Jim Fuller
On Mon, Apr 14, 2008 at 8:10 AM, Senaka Fernando <[EMAIL PROTECTED]> wrote:
>
> On Mon, Apr 14, 2008 at 6:33 AM, chromatic <[EMAIL PROTECTED]> wrote:
>
> > On Sunday 13 April 2008 08:14:11 Senaka Fernando wrote:
> >
> > > The build of Parrot fails with g++, which is a possible indication that
>
On Mon, Apr 14, 2008 at 12:26 AM, via RT Bob Rogers
<[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Bob Rogers
> # Please include the string: [perl #52858]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=52858 >
>
>
Bob Rogers wrote:
From: Alberto Simoes <[EMAIL PROTECTED]>
Date: Sun, 13 Apr 2008 19:16:39 +0100
This is my fault. I prefer smooth curves.
But I think smash can include the gplot data together with the source code.
That would be ideal.
>3. A semi-log plot would be easier
On Apr 12, 2008, at 17:37 , Moritz Lenz wrote:
[EMAIL PROTECTED] wrote:
Technically the Cartesian cross operator doesn't have an identity
value.
It has.
The set which contains only the emty set, or in perl terms ([]);
If (a, b) denotes an ordered pair you get
{0, 1} X {{}} = {(0, {}),
I'll be able to test Parrot in the next 48 hours
on my pentium mmx and tell you what the result is.
- Original Message -
From: "James Keenan via RT" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 14, 2008 5:36 AM
Subject: [perl #41095] [BUG] Segfault in test.exe during
>-Original Message-
>From: Mark A. Biggar [mailto:[EMAIL PROTECTED]
>Sent: Sunday, April 13, 2008 11:22 PM
>To: Miller, Hugh
>Cc: Moritz Lenz; p6l
>Subject: Re: cross operator and empty list
>
>Miller, Hugh wrote:
>>> From: Moritz Lenz [mailto:[EMAIL PROTECTED]
>>> [EMAIL PROTECTED] wro
# New Ticket Created by Reini Urban
# Please include the string: [perl #52870]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52870 >
Attached patch removes fixed issues from the TODO.
--
Reini Urban
http://phpwiki.org/
On Apr 14, 2008, at 12:05 , TSa wrote:
HaloO,
Xavier Noria wrote:
{0, 1} X {{}} = {(0, {}), (1, {})}
which, you see, is different from {0, 1}. They have different
elements. The fact that there's a clear mapping that sort of
identifies them has nothing to do with set equality.
But X is
HaloO,
Brandon S. Allbery KF8NH wrote:
our ::T sub foo (T $a, T $b)
without needing to introduce a new twigil syntax for type variables.
My reading as well. But I would write it sub foo (::T $a, T $b --> T)
for better indicating that ::T is taken from the parameters.
(Although I would won
HaloO,
Xavier Noria wrote:
{0, 1} X {{}} = {(0, {}), (1, {})}
which, you see, is different from {0, 1}. They have different elements.
The fact that there's a clear mapping that sort of identifies them has
nothing to do with set equality.
But X is cooperating with , in Perl 6:
(0,1) X
In Lua libraries, I wrote many time the same piece of code.
The purpose of this code is to register each function.
So, I try to write the following PIR macro :
.macro register(tname, fname)
.const .Sub $fname = .fname
$fname.'setfenv'(_lua__GLOBAL)
set
Hi all,
[#perl 52874] is a continuation of this issue. I guess I replied to the
wrong mail.
Regards,
Senaka
On Mon, Apr 14, 2008 at 3:50 PM, chromatic <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 14, 2008 at 11:40:01AM +0530, Senaka Fernando wrote:
>
> > On Mon, Apr 14, 2008 at 6:33 AM, chromatic <
IMCC's macro processor doesn't currently allow for uniquely generated
variable names. It's in the pdd (19), but not yet implemented.
You're right in that it only works for labels.
kjs
On Mon, Apr 14, 2008 at 1:32 PM, François Perrad
<[EMAIL PROTECTED]> wrote:
>
> In Lua libraries, I wrote many
Jerry wanted to verify it worked on windows when the required modules
were present. (Right now it fails, though in a somewhat graceful
manner.)
On Sun, Apr 13, 2008 at 10:38 PM, James Keenan via RT
<[EMAIL PROTECTED]> wrote:
> IIRC, Coke recently verified that parrotbug is working (even if not
>
On Sun, Apr 13, 2008 at 10:36 PM, James Keenan via RT
<[EMAIL PROTECTED]> wrote:
> Coke: Have we overcome this problem?
>
> kid51
>
>
I don't think so, no.
Try this:
% mkdir foo
% touch foo/bar.t
% svn add foo
% prove t/distro
Shouldn't this complain about:
- items that have been svn added but
On Mon, Apr 14, 2008 at 5:03 AM, Klaas-Jan Stol <[EMAIL PROTECTED]> wrote:
> IMCC's macro processor doesn't currently allow for uniquely generated
> variable names. It's in the pdd (19), but not yet implemented.
>
> You're right in that it only works for labels.
>
> kjs
>
>
>
>
> On Mon, Apr 14
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Apr 14 13:00:04 2008 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
On Sun, 13 Apr 2008, James E Keenan wrote:
> I recently obtained shell accounts on some Solaris boxes. Today I made my
> first attempt to compile and build Parrot on one of them.
>
> Configuration was very smooth. See log attached. Note for reference:
>
> Determining if your platform supports
On Mon, Apr 14, 2008 at 11:40:01AM +0530, Senaka Fernando wrote:
> On Mon, Apr 14, 2008 at 6:33 AM, chromatic <[EMAIL PROTECTED]> wrote:
> > Thanks, applied as r26965, except for the patch to
> > compilers/imcc/imclexer.c, which is a generated file. The source is
> > compilers/imcc/imcc.l.
> We
# New Ticket Created by "Senaka Fernando"
# Please include the string: [perl #52876]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52876 >
Hi all,
[#perl 52874] is a continuation of this issue. I guess I replied to the
wr
# New Ticket Created by "Senaka Fernando"
# Please include the string: [perl #52874]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52874 >
Attaching patch No. 2 for C++ Build Issue.
I still need to resolve this bigint.c i
On Mon, Apr 14, 2008 at 10:07:14AM +0100, Alberto Simoes wrote:
> Bob Rogers wrote:
> > From: Alberto Simoes <[EMAIL PROTECTED]>
> > >3. A semi-log plot would be easier to interpret.
> >
> > Smash tried a log plot, but it wasn't easier to interpret. I am not
> > sure what is a semi-log
# New Ticket Created by "Senaka Fernando"
# Please include the string: [perl #52886]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52886 >
Including gmp.h causes build break in C++ build on Ubuntu Gutsy. The problem
is som
On Mon, Apr 14, 2008 at 12:05:15PM +0200, TSa wrote:
> But X is cooperating with , in Perl 6:
>
> (0,1) X (()) === ((0,()),(1,())) === (0,1)
>
> That is, X strips the outer list and comma concatenates the
> inner empty list away.
No, the inner () is also in list context, and () in list context
a
On Sun, 13 Apr 2008, James E Keenan wrote:
> I recently obtained shell accounts on some Solaris boxes. Today I made my
> first attempt to compile and build Parrot on one of them.
> 'myconfig' and the output of uname are attached.
> [parrot] 52 $ uname -a
> SunOS 5.10 Generic_120011-14 sun4v
HaloO,
Larry Wall wrote:
No, the inner () is also in list context, and () in list context
always just disappears.
And 0,1 X () is going to be (). Perl 6's infix: is defined over
lists, not sets. If you want to overload X for set types, you may.
Then [X]() also is ()? How about (0,1) X ([])
I don't see any issue on my Gutsy build, and it seems that all tests
successfully pass. Therefore, perhaps this issue seems to be resolved.
Regards,
Senaka
# New Ticket Created by "Senaka Fernando"
# Please include the string: [perl #52888]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52888 >
Hi all,
I would like to make two improvements to the towers of hanoi sample.
1. U
HaloO,
I wrote:
Then [X]() also is ()? How about (0,1) X ([]) === (0,1)?
The original question was sort of about how to write a list
that has .elems == 1 but "no" content.
Other ideas are: [[]] and @@() with the latter not very likely
because it implies any multidimensional array somehow havin
Original Message
Subject: Re: macro PIR needs
Date: Mon, 14 Apr 2008 18:03:44 +0200
From: François Perrad <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: jerry gay <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
jerry gay wro
On Mon, Apr 14, 2008 at 06:28:06PM +0200, TSa wrote:
> HaloO,
>
> Larry Wall wrote:
>> No, the inner () is also in list context, and () in list context
>> always just disappears.
>>
>> And 0,1 X () is going to be (). Perl 6's infix: is defined over
>> lists, not sets. If you want to overload X fo
On Mon, Apr 14, 2008 at 06:28:06PM +0200, TSa wrote:
> The original question was sort of about how to write a list
> that has .elems == 1 but "no" content.
Wouldn't that just be [[]] ?
Mark J. Reed <[EMAIL PROTECTED]>
On Mon, Apr 14, 2008 at 12:54 PM, François Perrad
<[EMAIL PROTECTED]> wrote:
>
>
> Original Message
> Subject: Re: macro PIR needs
> Date: Mon, 14 Apr 2008 18:03:44 +0200
> From: François Perrad <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: jerry gay <[EMAIL PROTEC
Now would be a great time to work on updates to PLATFORMS so they're
ready for the release tomorrow.
Jerry is working on NEWS updates while in transit, but patches could
potentially be helpful there as well.
Thanks.
--
Will "Coke" Coleda
At 09:58 -0700 4/14/08, Larry Wall wrote:
>By the way, you don't need to put parens around the arguments to X. It takes a
>list on either side. We made it tall so that it would stand out visually
>anyway:
>
>$a,$b,$c X $x,$y,$z
How long before some engineer or 3D graphic artist gets really
On 2008-Apr-13, at 4:07 am, John M. Dlugosz wrote:
I'm thinking that 'constant' is more special than other variables,
and that the formal description of strong typing and static types
should say that the compiler =will= implicitly get the type for $pi
rather than making it Any.
Except if c
On Mon, Apr 14, 2008 at 11:47:04AM -0600, Doug McNutt wrote:
: At 09:58 -0700 4/14/08, Larry Wall wrote:
: >By the way, you don't need to put parens around the arguments to X. It takes
a list on either side. We made it tall so that it would stand out visually
anyway:
: >
: >$a,$b,$c X $x,$y,
I don't care for the use of * there, but it would be nice to have some
way to declare the variable to have the type implied by its
initializer, where the complier can tell what that is, so you could
remove the redundancy in this:
my Dog $fido = new Dog();
while still allowing the var declared via
Mark J. Reed wrote:
I don't care for the use of * there, but it would be nice to have some
way to declare the variable to have the type implied by its
initializer, where the complier can tell what that is, so you could
remove the redundancy in this:
my Dog $fido = new Dog();
while still allowin
On Mon, Apr 14, 2008 at 2:32 PM, Jonathan Worthington
> my Dog $fifi .= new(); # works in Rakudo too ;-)
And even in Pugs! :) Doesn't help with literals, though, e.g.
my Float $approx_pi = 3.14;
--
Mark J. Reed <[EMAIL PROTECTED]>
On Mon, Apr 14, 2008 at 4:00 PM, Senaka Fernando <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> C++ build succeeded, but with some tests failed. There were two issues that
> I couldn't formally sorted, and thus I had to tweak it. I have opened
> tickets for all other build related issues which have a for
Coke,
These are not intended to be applied. But, I doubt whether it is something
else. Here is the output of the Configure.pl, and a diff against the output
I get when I use gcc.
Also, here are some reasons to what might cause these errors.
1. these are either misuse of names
2. or due to __cplu
# New Ticket Created by Stephane Payrard
# Please include the string: [perl #52898]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52898 >
When I build on my macbook with macosx 10.5.2. I get the following error
ar: blib/l
as of r26974, i've updated the NEWS file for the release. it's been a
busy month, especially for languages. i've updated information on the
languages with which i'm most familiar, but your input is most
welcome. also, could somebody peruse the svn log since the last
release (r26484) and add update
Let me supply some data:
502 $ perl Configure.pl
Parrot Version 0.6.0 Configure 2.0
Copyright (C) 2001-2008, The Perl Foundation.
[# snip: need to configure so that Parrot::Test is available ]
Okay, we're done!
You can now use `make' to build your Parrot.
After that, you can use `make test' to
On Mon, Apr 14, 2008 at 10:21 AM, Will Coleda <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 14, 2008 at 12:54 PM, François Perrad
>
>
> <[EMAIL PROTECTED]> wrote:
> >
> >
> > Original Message
> > Subject: Re: macro PIR needs
> > Date: Mon, 14 Apr 2008 18:03:44 +0200
> > From:
Andy Dougherty wrote:
On Sun, 13 Apr 2008, James E Keenan wrote:
[snip]
/opt/SUNWspro/bin/CC -o miniparrot src/main.o \
-L/home/kid51/work/parrot/blib/lib -lparrot -lsocket -lnsl -ldl -lm
-lpthread -lrt -lgmp -lcrypto -L/usr/lib -L/usr/ccs/lib
-L/opt/SUNWspro/prod/lib/sparc -L/opt/SUNWs
Will check on all these things next time I get tuits for Solaris work.
PPC or Intel?
Could this be related to 52214?
# New Ticket Created by James Keenan
# Please include the string: [perl #52904]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52904 >
I'm filing this ticket as a marker to track all other tickets raising
issues about Mac
From: "Senaka Fernando" (via RT) <[EMAIL PROTECTED]>
Date: Mon, 14 Apr 2008 07:38:22 -0700
# New Ticket Created by "Senaka Fernando"
# Please include the string: [perl #52888]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket
I recommend that this ticket be closed. AFAICT from our smoke tests,
FreeBSD has no more failures in these tests than any other OS.
Certainly, there is no evidence of general failure.
Any objections?
kid51
Are we still experiencing this now that we're up to 0.6.0 (or 0.6.1)?
I believe tewk did a lot of work in this area since the last post. Does
the problem still occur?
Thank you very much.
kid51
For the record, we still have two tests SKIPped in this file:
$ prove -v t/stm/basic_mt.t
t/stm/basic_mt..
1..4
ok 1 - wait (simple)
ok 2 # SKIP Intermittent failures on all platforms
ok 3 # SKIP Intermittent failures on all platforms
ok 4 - wait + invalidate outer transcation
ok
All tests suc
Doug McNutt douglist-at-macnauchtan.com |Perl 6| wrote:
At 09:58 -0700 4/14/08, Larry Wall wrote:
By the way, you don't need to put parens around the arguments to X. It takes a
list on either side. We made it tall so that it would stand out visually
anyway:
$a,$b,$c X $x,$y,$z
H
To me the foo looks like a template sub and I wonder how it is
instanciated with different types. Since type parameters are
provided with [] it should be foo[Int], foo[Str] and the like.
I wonder further if that could also be written foo of Str like
with Array of Int etc.
my foo of Int &intfo
Mark J. Reed markjreed-at-mail.com |Perl 6| wrote:
On Mon, Apr 14, 2008 at 2:32 PM, Jonathan Worthington
my Dog $fifi .= new(); # works in Rakudo too ;-)
And even in Pugs! :) Doesn't help with literals, though, e.g.
my Float $approx_pi = 3.14;
So the idea of marking the use of
I posted my thoughts as a sort of white paper here:
http://www.dlugosz.com/files/static-type.pdf
This needs to be fleshed out. Decisions need to be made. Anyone want to
discuss it with me?
--John
# New Ticket Created by Jerry Gay
# Please include the string: [perl #52910]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52910 >
Placeholder and container for issues related to the 20 May 2008 release.
On Tue, Apr 15, 2008 at 7:37 AM, Bob Rogers <[EMAIL PROTECTED]>
wrote:
> From: "Senaka Fernando" (via RT) <[EMAIL PROTECTED]>
> Date: Mon, 14 Apr 2008 07:38:22 -0700
>
> # New Ticket Created by "Senaka Fernando"
> # Please include the string: [perl #52888]
> # in the subject line of al
Hi Mark,
Yes, if possible that would be great. Another is to change,
key_next(PARROT_INTERP, ARGIN(const PMC *key)) to key_next(PARROT_INTERP,
ARGIN(PMC *key)).
Regards,
Senaka
On Tue, Apr 15, 2008 at 10:20 AM, Mark Glines via RT <
[EMAIL PROTECTED]> wrote:
> On Mon Apr 14 04:50:02 2008, [EMAI
63 matches
Mail list logo
