I use fink for ease of installing dependencies(imagine the annoyance of
trying to install gimp when you don't have any of it's dependencies and
don't know which ones you need), and I could try making an info file
for parrot. One problem that I can already see is the tree that parrot
creates fo
equired to make Configure.pl more
flexible, I'm sure we can address those.
If you give me a list of what you need, I can work on the configure
changes to make it happen. I almost always work out of the svn
sandbox, so I don't normally touch this.
Thanks!
On Nov 12, 2005, at 1:16 PM,
I'm pretty sure it already is for when pir's compiled to pasm.
Joshua
On Nov 13, 2005, at 7:16 PM, Joshua Hoblitt wrote:
I think it would be better if we didn't overload the meaning of
'\s*#.*'
in PIR.
-J
--
On Mon, Nov 14, 2005 at 01:48:35AM +0100, Leopold Toetsch wrote:
On Nov 14, 2005,
In my of me learning to write(at this point read) c, I found a small
curses game that I ported to pir. I've been having serious trouble
with my iBook so I was just now able to test it on darwin. Both parrot
installations are 0.3.1. With OS X 10.3.9, I get a Bus Error.
Attatched is the crash
The problem seemed to be in the ncurses_life.imc file. At line 324, it
uses wattron but it either attron should be used, or STDSCR added to
the argument list. But, another problem. Under FreeBSD 5.4, I had to
edit ncurses.imc to comment out the whole libform section. I get this
error when i
The documentation thing I've noticed too. A big reason I use perl is
there's a lot of documentation and I was able to teach myself. That's
not very easy with a lot of other languages. I don't deal at all with
PAST because the best reference documentation would be
examples/past/hello.past and
Since it's not documented at all that I've seen, either for or against,
I'm wondering what's the arguments to macros are supposed to be.
Consider this code.
--
.const int TRUE = 1
.const int FALSE = 0
.macro IfElse(conditional, foo, bar)
unless .conditional goto .$else
.fo
I just wrote up the binarytrees test in pir, based on the c version.
Although I haven't waited more than twenty minutes yet, I can't get it
working with the argument being 16(what they test with) beyond printing
the first line. The results I'm getting, it's slow, and I don't have
enough ram.
M, Leopold Toetsch wrote:
On Dec 11, 2005, at 0:53, Joshua Isom wrote:
Since it's not documented at all that I've seen, either for or
against, I'm wondering what's the arguments to macros are supposed to
be. Consider this code.
.sub main :main
.IfElse(TRUE,
Are there plans to submit these tests?
leo
From the faq...
Please will you include my favourite language?
Maybe we will when you write 15 of the benchmark programs in your
favourite language, and contribute them to "The Computer Language
Shootout" :-)
From the all benchmarks page...
And r
On Dec 12, 2005, at 12:55 PM, Chip Salzenberg wrote:
Hm. Pondering...
* PIR is primarily a compiler target, not a human language. (Pasm,
in contrast, is an entirely non-human language.) So convenience is
not paramount.
But people will write in it. There are programmers who write
Because the random benchmark is used for a few other tests, I figured
I'd do it next. To do it the same way in pir is slow because it
requires putting a variable into a global register and retrieving it
900,000 times. I have three versions written up. One that's split
over two files, with on
ine is the c version is a while loop and mine's a do while loop, off
by one. Right now I'm getting around 1.8 seconds.
random.pasm
Description: Binary data
On Dec 12, 2005, at 4:47 PM, Leopold Toetsch wrote:
On Dec 12, 2005, at 21:55, Joshua Isom wrote:
Hmm. I think we ju
I've written up the fasta and knucleotide benchmarks. The knucleotide
takes 25 seconds, but since their benchmark says it's given an argument
of 2,500,000 and none of the programs use argv, and they all read from
stdin, I'm assuming the 2,500,00 is for the fasta benchmark and it's
output file.
There should be four attached files, the pair, random_single.pir, and
random.pir. If parrot's executed in the same directory as the files,
it'll work fine.
On Dec 12, 2005, at 11:58 PM, Brent Fulgham wrote:
Could you supply a single-file version with everything in it, along
with your "incl
I gave up on optimizing the read for knucleotides, but I did greatly
improve the sort. It's only used twice, but added a fair number of
lines just to get it in there, so it's more readability than anything
else. The bottleneck is reading in the file. Anyway, attached are
fasta.pir and knucle
Forgot the file.
revcomp.pir
Description: Binary data
On Dec 12, 2005, at 4:47 PM, Leopold Toetsch wrote:
Well, we dont't have a C-like static construct.
Today I remembered something I read about how pir handles pasm
registers, "PASM registers keep their register. During the usage of a
PASM register this register will be not get assigned
to."
I just finished three more shoot outs. Two are rather simple, a
floating point version of ack, and another that reads from stdin and
adds together the numbers on the lines. The third, is regex-dna. It
cheats a little, since as far as I know PGE doesn't have any regex
based substitutions even
I noticed a slight glitch with the regex-dna benchmark. The benchmark
spec says to account for case insensitivity. So I added the :i
modifier to the patterns and just stuck to the p6 rules. But using the
:i modifier makes it take over three times as long. Although for the
example and the fu
I've fixed a few of the japhs, 3-7. I didn't leave japh7.pasm
obfuscated any more than a japh should be.
japh3.pasm
Description: Binary data
japh4.pasm
Description: Binary data
japh5.pasm
Description: Binary data
japh6.pasm
Description: Binary data
japh7.pasm
Description: Binary
I just retried it and it seems to be my mistake, not escaping the
backslashes...
On Dec 16, 2005, at 10:00 PM, Patrick R. Michaud via RT wrote:
On Fri, Dec 16, 2005 at 04:08:27PM -0800, Joshua Isom wrote:
# New Ticket Created by Joshua Isom
# Please include the string: [perl #37965]
# in
I do tend to use the latest revision, rarely more than a day old. I've
made up a quick script to make parrot, mainly because I have gmp and
gdbm installed by fink. I have --optimized enabled now. I'm primarily
using and 800Mhz PPC, 512k cache. I rarely get any difference in
speeds between -
I applied the changes to the code, using capture for the initial strip.
I did use \> instead of but I didn't notice any real difference,
even when I profiled it. For the matching, using a capturing regex
didn't work well because it'd have to backtrace, which slowed it down
too much for the s
wrapper around each iub key. If I make my version and the
perl version print out the final sequence, they're identical.
On Dec 17, 2005, at 9:47 AM, Leopold Toetsch wrote:
Joshua Isom wrote:
Commented
out is code to use capturing regex to do it for the final
substitution. PGE seems faster
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 the same, or at least general
behavior.
The PIR syntax.pod file says that nested namespaces can be used by
separating namespaces with a semicolon, ala nested array/hash
structures. But the common writing convention seems to be along the
lines of perl5 packages with a double colon to separate. After looking
at the "find_global Foo::
On Jan 6, 2006, at 10:17 PM, Joshua Juran wrote:
On Jan 6, 2006, at 4:11 PM, Alberto Simoes via RT wrote:
This needs some more discussion. If we look to Perl, for instance, it
doesn't have a built-in copy. You should use either a module, or open
both files, copy contents, and close both files
The fix added to make the files in doc/ops readable by someone other
than root once installed seemed to be dependent on which version of
ExtUtils::Command was installed. I had 1.05 installed and it didn't
work, chmod wasn't exported by default. I did upgrade to 1.09 so it
worked properly, but
With the attached patch, which changes argv to be a
ResizableStringArray instead of an SArray, when argv reaches the pir
execution, four null strings are prepended to argv. Running parrot
with -D8 prints the argv without those four null strings. The comment
above the change indicates eventual
I tried building tcl today but got a failure in parrot, undefined
symbol. It happens when first outputting the first pbc. I did a
distclean and reconfigured without optimize or using ccache, but that
didn't help. 'make dynclasses-test' tests dynlexpad and foo without
problems(I did have to e
shua
On Jan 13, 2006, at 2:27 PM, Jonathan Worthington via RT wrote:
"Joshua Isom (via RT)" <[EMAIL PROTECTED]> wrote:
Recently we stopped linking extend.obj into dynclasses. The meaning
behind
this is that functions in extend.c should not be used in dynclasses;
leo
explai
With some recent additions to resizablestringarray.pmc, a perhaps very
old todo can now be taken care of. It makes the proper changes to
src/embed.c, and some necessary changes to tcl.pir(shift to a string
instead of a pmc) and m4.pir(remove the work arounds, part for SArray,
part for a fixed
ny similar problems? It might be specific to the gcc version.
If it works with FreeBSD 6.0, it shouldn't be too complicated to
disable shared objects for 5.4.
On Jan 12, 2006, at 4:17 PM, Joshua Isom (via RT) wrote:
# New Ticket Created by Joshua Isom
# Please include the string: [pe
Due to the SArray issues, and an imperfect workaround(ok, failing...),
the change isn't as seamless as I'd hope. But, it is a minor change.
And for tcl, one of the options would be beneficial for tcl(and other
language compilers that pass on arguments to another program). But I
haven't heard
What about the whole parrot/installable_parrot difference?
On Jan 16, 2006, at 5:33 PM, Jonathan Worthington wrote:
Ooh, nice catch - I'm to blame for the addition of those two functions
but (a) develop on Win32 where this likely wouldn't show up and (b)
don't have an installed Parrot anyway,
Having it be absolute makes more sense to me, but there likely will be
people who want relative. Maybe something like:
$P0 = get_namespace[;"Foo";"Bar"]
Where the empty part mean "current namespace here." Of course, then
it'd be really confusing because it's the opposite of pathnames
Currently, the .global directive for pir is unimplemented. Other than
being in the source code for the imcc compiler, it's absent. Is
.global intended to truely store to global, or be more like a mutable
constant, applicable to only that file(and then perhaps any that
.include it). If it
I've tested on FreeBSD 6.0 and OS X 10.3.9, and t/problematic.t is
successful for both, both with r11418.
But, I've encountered two major problems. On darwin, I can't finish
past_node.t, first parrot takes over 100 megs of ram, then perl(5.8.7)
wants 180 megs. On freebsd, it's actually worse
2006, at 17:33, Joshua Isom via RT wrote:
But, I've encountered two major problems. On darwin, I can't finish
past_node.t, first parrot takes over 100 megs of ram, then perl(5.8.7)
wants 180 megs. On freebsd, it's actually worse, but more confusing.
It fails with past_*.t and post
[29] (2), P0, I0 - , P0=PMCNULL,
I0=5289976
106 repeat S0, "", I0- , , I0=5289976
110 add I0, 1- I0=5289976,
DOD
GC
113 typeof S1, P0- , P0=Object(PAST::Node)=PMC(0x50ba68)
116 print S0 - S0=""
I sent a patch into rt, #38405, to address the make archclean issues,
so people could try it out. I'd only tested it on freebsd and darwin
and my main concern was with win32. It does a lot of restructuring to
help make it easier, and I wasn't sure how it'd be with windows.
On Feb 4, 2006, at
You use :optional to denote an optional parameter, and :opt_flag on an
int that is set to "true" if there's a parameter in :optional. The
fact that :opt_flag is optional could be construed to be a bug. But
all tests successful for me now for punie, and fairly quickly, so I'm
going to assume t
From what I can tell, the biggest concern is how different languages
will want it done. Why not allow it to be hll specific? Perhaps
either using a .HLL directive or perhaps a sub with a :hll_init or
something that is called whenever entering that hll, so strictness can
be defined per hll and
I guess this is one place where being CISC really is better than being
RISC. But how much improvement with outputting to a pbc first? But a
couple notes, there's no --help-optimize like --help-debug, and as far
as I know, there's no way to disable optimizations completely, e.g.
this pir
.su
But with jit enabled on x86/freebsd/openbsd, I was having problems with
some of the pow functions. The rt number is #38382. Because of the
compile time optimization, it made it trickier to work with because the
compile time was ok, but the jit runtime wasn't, and it took me a
little while to
Why not case it to switch it to 0x7fff? In any case, if the code's
added in to check for it an to throw an exception, then wouldn't it be
more friendly to return as close to what's expected, and just call it
"magical rounding"? But out of curiosity, why would integer division
be a floatin
I wrote up a quick patch to os.pmc to add an ls method. Pass it a
directory name, and it'll return a resizablestringarray with the
contents of the directory. But, I don't know anything about the
windows API and can't test it, etc... I don't think there's been any
decision yet on the interfac
On Feb 13, 2006, at 6:28 PM, Joshua Hoblitt wrote:
On Mon, Feb 13, 2006 at 08:09:45PM -, Jonathan Worthington wrote:
I agree with Chris on minimising the amount of places we do security
stuff
as far as is sensible. However, I would think that the interface for
doing
sandboxing style stuf
I'd say anything in languages/ should be ignored, because those should
be the responsibility of the language maintainer to test. But I've
just completed fixing all the broken pods(and a few that aren't invalid
bug are broken) except those in languages/, plus languages/t/harness.
I haven't com
And what about Null? And if they're not equal, what effect would that
have on sorting? Although for sorting, I guess that NaN != NaN would
have the some issue, but undef values in an array are more likely.
On Feb 20, 2006, at 4:34 PM, Joshua Hoblitt via RT wrote:
Can we get a design descisi
It was working on 11676, and I got it to build with 11686. But I
notice one problem: "Library not loaded:
/usr/local/lib/libparrot.dylib"
On darwin, if you want a shared parrot, you must set DYLD_LIBRARY_PATH
to include parrot's blib/lib.
For tcsh(os x default), it'd be "setenv DYLD_LIBRARY
riable declaration
as the effect is global until the end of the makefile.
-J
--
On Mon, Feb 20, 2006 at 06:40:24PM -0600, Joshua Isom wrote:
It was working on 11676, and I got it to build with 11686. But I
notice one problem: "Library not loaded:
/usr/local/lib/libparrot.dylib"
On darwi
The /usr/local/lib/libparrot.dylib says where the library should be.
Considering Apple choose to have shared library paths hard coded into
the executable, I'm not sure how they really handle DYLD_LIBRARY_PATH
to load the proper library. I haven't yet looked into which library
darwin uses, the
The main flag sets for speed are -C, -Cj, -S, -Sj, -j, and sometimes
adding -Oc as well. On ppc, -C and -Cj are often the fastest. On x86,
-j is most often the fastest. But here's the cavaet, to use JIT, you
of course need someone to port it to that arch. With -C, your compiler
has to suppo
How do you verify that a print succeeded? Currently there's no way to
know. Throwing an exception if a global flag is set would suffice and
wouldn't require constantly pushing exception handlers in case the
program doesn't care enough (e.g. the run it and delete it variety).
Plus using excep
On Mar 5, 2006, at 1:46 PM, Nicholas Clark wrote:
On Fri, Mar 03, 2006 at 11:27:05AM -0800, Allison Randal wrote:
Should the network opcodes even be loaded as standard? C et al
aren't
actually that useful on Perl 5 without all the constants in the Socket
module,
so in practical terms a redes
On Mar 5, 2006, at 3:46 PM, Nicholas Clark wrote:
On Sun, Mar 05, 2006 at 02:53:29PM -0600, Joshua Isom wrote:
A pasm include, such as the signal.pasm(even though signals don't work
yet), would suffice and is generated at compile time. Parsing .h
files
This way does the numeric valu
I finally got around to writing up a patch to parrot that would allow
the features I mentioned a while back. There aren't any heuristics,
just braces. The first file is a patch to imcc.l and imclexer.c(may as
well). The second file is a set of macro's I've already written up(not
documented p
On Mar 6, 2006, at 5:31 PM, Allison Randal wrote:
On Mar 6, 2006, at 4:08, Leopold Toetsch wrote:
* opcode vs function / method
open P0, "data.txt", ">"
print P0, "sample data\n"
Using opcodes for all the IO has some disadvantages:
a) namespace pollution: all opcodes
I've committed it as of r11820. Since it parses by tokens, braces
inside of strings are allowed.
With regard to clashing, pir specials take precedent over macros. The
complications that could arise from accidental recursion, etc, seems
complex. As for your .local example, you can always use
If the compiler goes through all the constants at compile time to find
identical ones, why not use ".const float number = 0.0"? With pmc's,
only .Sub is supported I think. But for more complex types, the best I
can think of is being able to freeze a pmc and store it into the const
table, such
I think it's gcc 3.3.5 and x86 specific. I'm not positive about the .5
though. I've been building on darwin ppc with 3.3 and it's fine, and
it fails on openbsd too. But it's also successful on gcc 4.1. I've
addressed it with using sprintf, since 1.22461e-16 is close enough to
0.00 f
On OpenBSD 3.8 x86, I still get the failures with -0.0/0.0. Check the
smokes...
On Mar 21, 2006, at 3:01 PM, Joshua Hoblitt wrote:
On Tue, Mar 21, 2006 at 06:42:42AM -0800, Steve Peters via RT wrote:
[jhoblitt - Sun Jan 01 18:49:23 2006]:
I've commited a possible fix for openbsd, cygwin, &
at version of OpenBSD were you running (perhaps something old or
direct from CVS)?
-J
--
On Tue, Mar 21, 2006 at 03:13:18PM -0800, Joshua Isom via RT wrote:
On OpenBSD 3.8 x86, I still get the failures with -0.0/0.0. Check the
smokes...
On Mar 21, 2006, at 3:01 PM, Joshua Hoblitt wrote:
On Tue, Ma
Multimethod constructors? That's one thing that, as far as I know, is
missing from parrot and could be resolved with this. Although the
potential to create an array for sprintf with one opcode does sound
nice, or at least one line of pir.
On Mar 24, 2006, at 11:38 AM, Chip Salzenberg wrote:
On Feb 7, 2007, at 1:49 PM, chromatic wrote:
On Tuesday 06 February 2007 15:56, James Keenan wrote:
On Feb 6, 2007, at 12:07 PM, Allison Randal wrote:
E ... I'm the one who *needs* the tutorial, not the one to write
it.
That makes you a prime person to capture the questions it needs to
On Feb 13, 2007, at 1:28 PM, Aldo Calpini wrote:
whoa there!
furthermore, the Configure process uses $^O here and there, and this
should eventually be replaced by an --arch=something parameter to
Configure.pl (which defaults to $^O, of course).
my parrot does indeed run some of the examples
On Feb 18, 2007, at 7:14 PM, Will Coleda wrote:
On Feb 17, 2007, at 10:14 AM, Patrick R. Michaud via RT wrote:
Yes, but our MANIFEST is just a list of everything in the repository
(modulo a single directory that we started skipping in r12600).
It's best purpose is probably to make sure tha
On Feb 19, 2007, at 5:57 PM, Nicholas Clark wrote:
There's a benchmark of Ruby implementations at
http://www.antoniocangiano.com/articles/2007/02/19/ruby-
implementations-shootout-ruby-vs-yarv-vs-jruby-vs-gardens-point-ruby-
net-vs-rubinius-vs-cardinal
(or http://xrl.us/uy5m )
There's a c
On Feb 20, 2007, at 8:44 AM, jerry gay wrote:
On 2/20/07, Aldo Calpini <[EMAIL PROTECTED]> wrote:
no objection here! this is a long-desired feature, and is currently
unavailable. although i don't have a pocketpc to test on, i'll do my
best to help. for years, the dependence on perl 5's configur
On Mar 4, 2007, at 12:40 PM, Alek Storm wrote:
For the same reason we have set_attr, set_attr_str, get_attr, and
get_attr_str, even though they're only used by ParrotObject - it
allows for
multiple, concurrent object systems. This goal is mentioned in PDD
15, in
"What The Bytecode Sees". Why
to memory management and the garbage collector.
On Mar 1, 2007, at 2:21 PM, Joshua Isom (via RT) wrote:
# New Ticket Created by Joshua Isom
# Please include the string: [perl #41658]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.htm
to memory management and the garbage collector.
On Mar 1, 2007, at 2:21 PM, Joshua Isom (via RT) wrote:
# New Ticket Created by Joshua Isom
# Please include the string: [perl #41658]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.htm
Two quick questions, what "hackish" things in pir are you refering to,
and how much more do you think it would take to get bytecode working?
Also, consider that file size alone is not the best indicator of how
well something is programmed, as sometimes a bigger object file is
faster than a sma
On Mar 23, 2007, at 7:51 AM, Mike Mattie wrote:
On Wed, 21 Mar 2007 18:39:51 -0700
Allison Randal <[EMAIL PROTECTED]> wrote:
chromatic wrote:
Agreed. And we don't work from the installation paths because the
installation paths are broken. Can we break out of this cycle with
some automated tes
On Mar 25, 2007, at 9:34 PM, James Keenan (via RT) wrote:
# New Ticket Created by James Keenan
# Please include the string: [perl #42082]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42082 >
Ongoing refactoring of Confi
Perhaps this is too complicated a method. The shootouts should
probably be ran with the testing core. If you want to test the CGP
core, use 'make testC', and so on. Otherwise, how will we know if
ack.pir starts failing with a different runcore? I'd feel it'd be
preferable to ignore the firs
On Mar 29, 2007, at 10:14 PM, Will Coleda wrote:
On Mar 27, 2007, at 4:45 PM, Allison Randal wrote:
but, we need better smoke tools
So lets document what we need. Right now 'make smoke' generates an
HTML report which is uploaded to the smoke server.
Talk has happened in
On Mar 29, 2007, at 4:20 PM, jerry gay wrote:
On 3/29/07, Nicholas Clark <[EMAIL PROTECTED]> wrote:
> and i'm not interested in testing every
revision,
> when so many might be coding standards
Why are people even checking things in that fail coding standards?
because not a
On Mar 30, 2007, at 9:19 PM, chromatic wrote:
On Friday 30 March 2007 13:59, Alek Storm wrote:
I used a simple benchmark to compare the relative speeds of Parrot
with and without the patch, and I was surprised to find that the test
script runs (very roughly) 10% faster *with* the patch. Can s
I'm trying to use libc to be able to do a directory listing, and and if
I used the DATATYPE_CSTR I get a segfault, and if I use
DATATYPE_STRING, I get a "returning unhandled string type in struct".
I don't know if I'm doing the calls wrong or what since the
documentation is vague in places. p
I'm on FreeBSD 5.4 so aside from the char array, the rest was correct,
which I guess means it's not at all portable. It's working now, now I
just need to expand on it.
On Nov 3, 2005, at 9:01 AM, Leopold Toetsch wrote:
Joshua Isom wrote:
I'm trying to use libc to be ab
I was trying to use bit shifting for division by multiples of two, but
if the shift amount is a multiple of the int size, it seems to fail to
shift the bits. Here's some example code demonstrating it.
.sub _main @MAIN
.local int a, b, c
print "a\tb\tc\n"
a = 24
b = 32
c = a
But why should the result be an unportable/undocumented parrot op? If
parrot's aiming for portability, so long as external libraries aren't
used, shouldn't parrot treat code the same way for all platforms?
Otherwise, each compiler for parrot would have to add in code to find
out the size of i
On Mar 31, 2007, at 3:24 PM, Allison Randal wrote:
Jonathan Worthington wrote:
Does this also imply that all number-based type instantiation is
going away, and thus we need to deprecate the find_type op too?
Eventually, yes (almost certainly), but not in the next month.
Allison
I'm not su
On Apr 3, 2007, at 11:29 PM, Will Coleda (via RT) wrote:
# New Ticket Created by Will Coleda
# Please include the string: [perl #42293]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42293 >
These two scripts perform the s
On Apr 4, 2007, at 6:39 AM, Paul Cochrane wrote:
On 04/04/07, Joshua Isom <[EMAIL PROTECTED]> wrote:
On Apr 3, 2007, at 11:29 PM, Will Coleda (via RT) wrote:
> # New Ticket Created by Will Coleda
> # Please include the string: [perl #42293]
> # in the subject lin
On Apr 5, 2007, at 10:45 AM, Klaas-Jan Stol wrote:
jerry gay wrote:
i've recently committed (r17998) a draft of PMC documentation
guidelines, for your review. This document is meant to formalize,
clarify, and extend the current de facto style for documentation of
core PMCs. you'll find the docu
On Apr 5, 2007, at 5:45 PM, Leopold Toetsch wrote:
Am Donnerstag, 5. April 2007 00:39 schrieb Jonathan Worthington:
Don't really need a policy to tell me that breaking stuff for
languages
folks sucks. :-) I try hard to avoid it, but unfortunately stuff slips
through the net occasionally. In t
On Apr 6, 2007, at 11:48 AM, chromatic wrote:
On Friday 06 April 2007 00:58, Joshua Isom wrote:
What if we had a repository, ala pugs with it's "open" commits, solely
for people to commit tests. It could help improve bug discovery and
test coverage, as well as ambiguity ab
On Apr 10, 2007, at 2:05 AM, Allison Randal wrote:
Klaas-Jan Stol wrote:
hi,
Some suggestions for PDD15:
1.
reading PDD15, I noticed that some methods/ops are named using an
underscore to separate words, others don't, for instance:
* get_class (but also "getclass" is used in the examples)
* n
On Apr 12, 2007, at 9:29 AM, Nicholas Clark wrote:
On Thu, Apr 12, 2007 at 09:13:14AM -0500, Steve Peters wrote:
On Thu, Apr 12, 2007 at 01:37:24PM +0200, Ron Blaschke wrote:
I think that we need to tread very carefully with adding additional
gcc-isms to Parrot, lest we break compatibility wi
On Apr 12, 2007, at 1:54 PM, Nicholas Clark wrote:
On Thu, Apr 12, 2007 at 01:50:09PM -0500, Joshua Isom wrote:
On Apr 12, 2007, at 9:29 AM, Nicholas Clark wrote:
My view of this is something along these lines. You can use any
function you want at all, but if it's not documented as
On Apr 14, 2007, at 7:44 AM, Jonathan Worthington wrote:
Hi,
This patch broke the build on some platforms (Win32 with MSVC++
included).
INTVAL
PIO_poll(Interp *interp, PMC *pmc, INTVAL which, INTVAL sec, INTVAL
usec)
{
+if (pmc == PMCNULL) {
+ real_exception(interp, NULL, E_Valu
On Apr 16, 2007, at 8:46 AM, Andy Dougherty wrote:
On Sun, 15 Apr 2007, Allison Randal via RT wrote:
According to our records, your request regarding
"[TODO] ResizableBooleanArray uses 64 bytes per bit of information"
has been resolved.
If you have any further questions or concerns, please
On Apr 16, 2007, at 8:46 AM, Andy Dougherty wrote:
On Sun, 15 Apr 2007, Allison Randal via RT wrote:
According to our records, your request regarding
"[TODO] ResizableBooleanArray uses 64 bytes per bit of information"
has been resolved.
If you have any further questions or concerns, please
On Apr 18, 2007, at 3:48 PM, chromatic wrote:
On Wednesday 18 April 2007 13:34, Alek Storm wrote:
Vtable methods defined in C are visible from C.
Of course, otherwise nothing would be able to call them.
Therefore, it makes
sense that vtable methods defined in PIR are visible from PIR, at
On Apr 19, 2007, at 8:18 PM, Patrick R. Michaud wrote:
On Thu, Apr 19, 2007 at 11:47:55AM -0700, Andy Dougherty wrote:
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #42620]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/r
On Apr 20, 2007, at 9:18 AM, Andy Dougherty wrote:
On Thu, 19 Apr 2007, Patrick R. Michaud via RT wrote:
On Thu, Apr 19, 2007 at 11:47:55AM -0700, Andy Dougherty wrote:
t/compilers/pge/p5regex/p5rx.Parrot VM: PANIC: Out of
mem!
I believe that both of these tests are currentl
1 - 100 of 163 matches
Mail list logo
