We've got a couple new hoplites out there, so check out the status page.
http://qa.perl.org/phalanx/status.html
Also, Paul Johnson has some slick stuff on CPAN module coverage that
should be interesting for new hoplites to take a look at, to see
which modules are covered least. Percentage asid
On Sun, Oct 12, 2003 at 06:28:52PM +0200, Gabor Szabo wrote:
> That is, both test.pl and t/*.t were executed.
AFAIK its always been this way. DBI relies on it.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
It should indeed be said that notwithstanding the fact t
At 08:46 PM 10/12/2003 +0200, Leopold Toetsch wrote:
Melvin Smith <[EMAIL PROTECTED]> wrote:
> At 12:07 PM 10/12/2003 +, Leopold Toetsch wrote:
>> -Bytecode
>> -
>> -- Byteordering works for most stuff except floating point (N regs)
>> - Cross platform bytecode doesn't convert floats y
Gregor N. Purdy <[EMAIL PROTECTED]> wrote:
> .local str s
a lot of problems you have (and Luke already hinted at that) seems to be
the syntax of .sym (or .local) - I prefer .sym because .local is used
for local macro lables too hysterically.
So we have:
.sym int I_REG
.sym fl
The tinders are all failing to be ablaze, yet still failing horribly,
with the compilation of dynext.c whining about a missing
enum_class_ConstParrotLibrary. (I note that local builds for me are
complaining about the same problem)
Since there's no constparrotlibrary.pmc in the repository, I'm
Gregor N. Purdy writes:
> Luke --
>
> Yeah. That falls into the "duh" category, I guess.
>
> But, I'm still having some trouble:
>
>
> .pcc_sub _consume_string prototyped
> .param str input
.param string input
Now the error makes sense.
> .local int c
> .local int test
>
> .loca
At 7:01 PM +0200 10/10/03, Juergen Boemmels wrote:
So i think it would be better to let PIO_seek return the current
offset. So I purpose a change of the prototype of PIO_seek to
If you've not already done this, go ahead. (I'm a bit behind :)
--
Dan
--
Luke --
Yeah. That falls into the "duh" category, I guess.
But, I'm still having some trouble:
.pcc_sub _consume_string prototyped
.param str input
.local int c
.local int test
.local Sub __char_is_white_space
newsub __char_is_white_space, .Sub, _char_is_white_space
.local Sub __
Gregor N. Purdy writes:
> Leo --
>
> The Jako compiler spits stuff out from Perl.
>
> I'm writing some new experimental stuff in PIR directly.
>
> I'm curious about other stuff, too. I don't see any
> of the languages/imcc/t/**/*.t files doing anything with
> the ord op, and when I try to use it
Leo --
The Jako compiler spits stuff out from Perl.
I'm writing some new experimental stuff in PIR directly.
I'm curious about other stuff, too. I don't see any
of the languages/imcc/t/**/*.t files doing anything with
the ord op, and when I try to use it as
.local int c
.local str s
and th
Gregor N. Purdy <[EMAIL PROTECTED]> wrote:
> .pcc_call char_is_white_space ### "unexpected identifier"?o
[snip ]
> .char_is_white_space(c)
> if test goto ...
The macro better should take the test result too:
.CHAR_IS_WS(c,test)
> Except, the line marked in the macro def above shows that
Gregor N. Purdy <[EMAIL PROTECTED]> wrote:
> Is there any good reason why prototyped PCC subs
> shouldn't be callable with IMC syntax that looks like
> a macro call, without having to make a macro wrapper
> manually?
Could be done, but for sure unlikely. PASM/PIR are still assembler
languages. You
Melvin Smith <[EMAIL PROTECTED]> wrote:
> At 12:07 PM 10/12/2003 +, Leopold Toetsch wrote:
>> -Bytecode
>> -
>> -- Byteordering works for most stuff except floating point (N regs)
>> - Cross platform bytecode doesn't convert floats yet
>> -
> Leo, I assume this works now since you r
On Sun, Oct 12, 2003 at 01:08:39PM +, Mark Stosberg wrote:
> I'm excited to see that the Phalanx project is happening.
>
> On the website I see this unfiled item:
>
> "Use Devel::Cover and gconv".
>
> One way that seems useful to use Devel::Cover is to have an automated coverage
> testing s
I was already talking to Leo offline a bit about refactoring some
of the IMCC syntax. We have incrementally added some
features at different times that could be handled with a more
compact syntax if we rework it.
1) Combine .pcc_sub and .sub and go back to using
the single keyword .sub.
*This m
Is there any good reason why prototyped PCC subs
shouldn't be callable with IMC syntax that looks like
a macro call, without having to make a macro wrapper
manually? (I know its not the way it works now, but
you can almost simulate it with a PCC sub def and a
macro, and it seems to me it would be n
I have a PCC sub:
.pcc_sub _char_is_white_space prototyped
.param int c # Character to test (as an integer representing its ASCII
code)
I was under the impression (I think I read it somewhere) that when
running "make test" if there is a test.pl file and a set of tests
in t/*.t only the former (test.pl) will run an the t/ directory
will be skipped.
I have just checked it and it seems to be not true.
That is, both test.pl and t/*.
On Sun, Oct 12, 2003 at 01:08:39PM +, Mark Stosberg wrote:
> A second sticking point could be that code is OS-specific, so it's not ever going
> to get testing by just one build machine.
And also, in the case of things like Class::DBI, have database specific
code in them, that is tested, but c
I'm excited to see that the Phalanx project is happening.
On the website I see this unfiled item:
"Use Devel::Cover and gconv".
One way that seems useful to use Devel::Cover is to have an automated coverage
testing system that would test the 100 module periodically.
All the phalanx page, an ex
20 matches
Mail list logo
