Joshua Isom wrote:
> ... proposing to change all floats to nums ...
I have no objection to the proposed change - but it would be interesting
to know the motivation behind this proposal. In some languages,
'num'/'number'/'numeric'/'bignum' implies decimal arithmetic and
'float'/'real'/'double' impl
On Dec 19, 2005, at 20:31 , Joshua Isom wrote:
I was talking to Leo in the IRC room and he told me post onto the
list about proposing to change all floats to nums. Code such as
`.local float i` would instead be written as `.local num i`, but as
I gather it, current behavior would remain t
On Dec 20, 2005, at 4:01, Joshua Hoblitt wrote:
I'm surprised that Parrot's memory usage is so high relative to other
platforms. It looks like a hog even relative to Java. Has anyone
taken
a serious look at where all that memory is going?
Memory usage as well as startup time aren't optimi
On Dec 20, 2005, at 1:35, Brent Fulgham wrote:
FYI, the revised shootout updates are on the site:
http://shootout.alioth.debian.org/sandbox/benchmark.php?
test=all&lang=parrot
Yeah, I've seen it. Thanks a lot for updating all.
Performance seems much better with the interpreter
flags sugge
In it's current form ChangeLog is little more than a pointer to NEWS.
This is really defeating the purpose of what ChangeLog is supposed to
contain; detailed information about changes. It is also more or less
redundant with the function of NEWS. However, I am not proposing that
people start addin
On Tue, Dec 20, 2005 at 02:03:44AM -1000, Joshua Hoblitt wrote:
> people start adding detailed information to ChangeLog. I think it is
> entirely reasonable to machine generate this file with svn2cl[1] before
> each release. Comments?
Generating it from the subversion commit messages seems a go
On 12/15/05, Troy Denkinger <[EMAIL PROTECTED]> wrote:
>
>
> I wrote a test harness - you'll find the code below my signature, if
> you're interested. When I run it, I get the following:
>
> You said to run 0 tests! You've got to run something.
> # Looks like your test died before it could output
On 12/19/05, Troy Denkinger <[EMAIL PROTECTED]> wrote:
> The error is related to my pod.t which is, just as in the docs:
>
> use Test::More;
> eval "use Test::Pod 1.14";
> plan skip_all => "Test::Pod 1.14 required for testing POD" if $@;
> all_pod_files_ok();
>
> Running this under my test harness
As a parrot user, I have two feelings about this proposal 1) A very
small part of me thinks that this would improve a small consistency
nit which I've already lived with for... 4 years? 2) A much larger
part would find it another inconvenience in a long line of (each one
justifiable in its
Anything that makes it easier for developers to develop is a good thing.
On Dec 20, 2005, at 7:40 AM, Nicholas Clark wrote:
On Tue, Dec 20, 2005 at 02:03:44AM -1000, Joshua Hoblitt wrote:
people start adding detailed information to ChangeLog. I think it is
entirely reasonable to machine gene
On 12/20/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> In it's current form ChangeLog is little more than a pointer to NEWS.
> This is really defeating the purpose of what ChangeLog is supposed to
> contain; detailed information about changes. It is also more or less
> redundant with the functio
On Dec 19, 2005, at 8:31 PM, Joshua Isom wrote:
>I was talking to Leo in the IRC room and he told me post onto the
>list about proposing to change all floats to nums. Code such as
>`.local float i` would instead be written as `.local num i`, but as
>I gather it, current behavior would remai
Michael G Schwern wrote:
That's an error from Test::Builder (ie. the thing behind Test::More and
others) and not Test::Harness. Its coming from the test program your
harness is running, not from the harness itself.
[snip]
Thanks, Michael. I'll try that.
Regards,
Troy
*sigh*
Please don't apply this patch ... It causes the most recent svn tree to
segfault when trying to build PGE:
gmake[1]: Leaving directory `/home/steveg/parrot/src/dynclasses'
gmake -C compilers/pge
gmake[1]: Entering directory `/home/steveg/parrot/compilers/pge'
../../parrot mklib.pir >PGE/Li
I have released "Amber for Parrot" version 0.4.0 (Induction):
Downloads: http://xamber.org/download.html
Release history: http://xamber.org/history.html
Project home page: http://xamber.org/index.html
"Amber for Parrot" is an Eiffel-like scripting language for the Parrot
Virtual Machine.
Changes
The errors reported by valgrind have also gone in the latest SVN
release. This now seems to be a non-issue. 8-)
On Dec 20, 2005, at 16:45, jerry gay wrote:
... automatic generation sounds great, but it's no good
without clear commit messages. one or two word commit messages should
be shunned in favor of brief yet clear descriptions of the change,
including which parrot components are affected.
here are
On Tue, Dec 20, 2005 at 07:45:30AM -0800, jerry gay wrote:
> On 12/20/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> > In it's current form ChangeLog is little more than a pointer to NEWS.
> > This is really defeating the purpose of what ChangeLog is supposed to
> > contain; detailed information a
On Tue, Dec 20, 2005 at 11:56:17PM +0100, Leopold Toetsch wrote:
> I've tried that mentioned svn2cl util for the 50 last revs. Due to file
> moves or other global changes a lot of the created ChangeLog entries
> are a meaningless mess of a list of filenames + an "oneliner". If I
> need this I ca
# New Ticket Created by Steve Gunnell
# Please include the string: [perl #37992]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37992 >
It hasn't fixed my Segfaulting but along the way valgrind was reporting
a lot of error
# New Ticket Created by jerry gay
# Please include the string: [perl #37993]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37993 >
compiling either with msvc 6.0 or 7.1 on win32, parrot behaves
differently wrt 0 vs -0 dep
> I think that sort of metadata is more appropriate for an RT ticket. A
> commit messages should describe primarily * what* is being changed
> instead of *why* the change is being made. Of course, including the
> *why* doesn't hurt but I don't believe it should be part of our
> guidelines.
(Th
# New Ticket Created by Justin Koser
# Please include the string: [perl #37997]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37997 >
Hello Parrot hackers,
I'm trying to build Subversion revision 10604 of Parrot on Cygwi
Following the discussions from 2 weeks ago, are there any plans to
update the synopsis soon regarding the $! variable? Synopsis 2 still
says that it is conjectural to whether $! is always environmental.
Thanks. -- Darren Duncan
24 matches
Mail list logo
