Dan wrote:
> Should be FINALIZE.
Although some in the non-US English speaking world might say it should
be FINALISE.
Perhaps FINAL might be a better choice? That would please more of the
people for more of the time (or displease them for less of the time).
A
Chromatic <[EMAIL PROTECTED]> wrote:
> On Sun, 2004-04-04 at 00:28, Leopold Toetsch wrote:
>> Object gurus, please have a look at t/pmc/object-meths_17. Is the code
>> ok? Is it failing because init order is really wrong?
>>
>> BTW I tried to add this test as a TODO but this seems not to work.
>
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Togos <[EMAIL PROTECTED]> wrote:
>
>> $I1 = $I2 + $I3
>
>> $P1 = $P2 + $P3
>
>> Which, of course, doesn't work. But this is what
>> languages like Python or Ruby would expect to be able
>> to do, as they don't need Perl's fancy variable
>> objects
On Wednesday 07 April 2004 08:19, Leopold Toetsch wrote:
> Looks good. Should it go into CVS?
Yes it can.
> BTW: some Cs still survived.
getprop? I found two delprops, removed.
Can I get commit privs?
I also have a Data::Dumper patch nearly ready that removes the F
and F usage. It is very time c
Marcus Thiesen wrote:
as I pointed out in my "Parrot on Alpha" post I had to do a change to the
OpenBSD platform.h file in order to get it to run on other platforms. As I
ran now into the same problem giving parrot a try on a Vax, I think this
might be worth commiting.
Thanks, applied.
leo
I'd like to separate functions of interpreter.c into distinct files
(it's currently more then 2500 lines):
init ... init destroy
cb ... callback function handling
run_loop ... runloop selection
run_fromc ... call runloop from c
load_ops ... dynamic oplib loading
...
Which scheme should be used
Hi,
On Wednesday 07 April 2004 08:50, Leopold Toetsch wrote:
> - runtime/parrot/*/
This directory does only include generated files, doesn't it?
> - library/
Maybe move it to runtime/library?
We can also create a runtime/t/ (or t/runtime) where the library tests can go
to.
> 1) We should probabl
Jens Rieks <[EMAIL PROTECTED]> wrote:
> Can I get commit privs?
That would be the best.
leo
Piers Cawley <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch <[EMAIL PROTECTED]> writes:
>> That and other arguments are of course all correct. I just have the gut
>> feeling that having both opcode and vtable variants blows core size up
>> to an isane value.
> Couldn't you have a single opcode, C,
On Wed, Apr 07, 2004 at 08:15:03AM +0100, Andy Wardley wrote:
> Dan wrote:
> > Should be FINALIZE.
>
> Although some in the non-US English speaking world might say it should
> be FINALISE.
FYI: FINALIZE is the spelling used by the Oxford English Dictionary.
See http://www.askoxford.com/asktheexp
Jens Rieks <[EMAIL PROTECTED]> wrote:
> Hi,
> On Wednesday 07 April 2004 08:50, Leopold Toetsch wrote:
>> - runtime/parrot/*/
> This directory does only include generated files, doesn't it?
Almost. We have in CVS:
- runtime/parrot/include/DWIM.imc
- runtime/parrot/include/Getopt_Long.imc
- runti
The Perl 6 Summary for the week ending 2004-04-04
Wednesday? Why did I leave it 'til Wednesday to write the summary? I
must have *some* reason. Or maybe not. I'll give fair warning that I
won't be doing a summary for next week though, what with Easter and
everything, but you'll get
The Perl 6 Summarizer <[EMAIL PROTECTED]> wrote:
> Subroutine calls
> Leo announced that he's added a "pmc_const" opcode to parrot. The idea
> being that, [ ... ]
> you would instead fetch a preexisting Subroutine PMC
> from the PMC constant pool.
Not quite. I've implemented it
--- Piers Cawley <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch <[EMAIL PROTECTED]> writes:
>
> > Togos <[EMAIL PROTECTED]> wrote:
> >
> >> $I1 = $I2 + $I3
> >
> >> $P1 = $P2 + $P3
> >
> >> Which, of course, doesn't work. But this is what
> >> languages like Python or Ruby would expect to be
>
We currently have and ops that work with the
user stack, and and that work with the
register stacks, and which are equivalent to:
pushi
pushn
pushs
pushp
and
popi
popn
pops
popp
respectively. Wouldn't a better name for the latter be and
, to avoid any conf
Jens Rieks <[EMAIL PROTECTED]> wrote:
> here is a working version of my new Stream library. I will add more
> documentation later this month, the examples should be enough to
> understand the usage.
I'm currently investigating a bunch of SIGSEGVs when tracing the examples.
They are all coming fr
On Wed, 2004-04-07 at 00:23, Leopold Toetsch wrote:
> $ perl -Ilib t/pmc/object-meths.t
> 1..17
> ...
> not ok 17 - constructor - diamond parents # TODO wrong init order?
> # Failed (TODO) test (t/pmc/object-meths.t at line 469)
> ...
>
> $ perl -Ilib t/harness t/pmc/o*.t
> t/pmc/object-meths
At 6:04 PM -0400 4/6/04, Randy W. Sims wrote:
On 4/6/2004 11:06 AM, Dan Sugalski wrote:
At 6:12 AM -0400 4/4/04, Randy W. Sims wrote:
[Scheme 1: hierarchy munging]
[Scheme 2: loadable-library style plugins]
Is there anything in the above that stands out as potentially
being problematic?
Well, t
# New Ticket Created by Jeff Clites
# Please include the string: [perl #28344]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=28344 >
On Mac OS X, the test below is failing. It appears that the
initialization order is i
On Wednesday 07 April 2004 17:42, Leopold Toetsch wrote:
> Jens Rieks <[EMAIL PROTECTED]> wrote:
> > here is a working version of my new Stream library. I will add more
> > documentation later this month, the examples should be enough to
> > understand the usage.
>
> I'm currently investigating a
Chromatic <[EMAIL PROTECTED]> wrote:
> It's possible to customize this, if you want, or to write a tool looking
> for TODO tests, but this is the default, expected behavior.
I know. But it's more or less useless, when TODO tests are hidden in the
result. No one will look at these tests.
What abo
On Tue, Apr 06, 2004 at 06:04:56PM -0400, Randy W. Sims wrote:
> On 4/6/2004 11:06 AM, Dan Sugalski wrote:
> >At 6:12 AM -0400 4/4/04, Randy W. Sims wrote:
> >[Scheme 1: hierarchy munging]
> >
> >[Scheme 2: loadable-library style plugins]
> >
> >>Is there anything in the above that stands out as po
It has taken me longer than I expected to carve out some time to work
on finishing my ICU/string patch, but it's progressing now, and I just
finished tracking down some bugs of mine that the config_lib.pasm stuff
was exercising. So I'm currently back to the state of passing all
expected tests (
At 10:27 AM -0700 4/7/04, Jeff Clites wrote:
It has taken me longer than I expected to carve out some time to
work on finishing my ICU/string patch, but it's progressing now, and
I just finished tracking down some bugs of mine that the
config_lib.pasm stuff was exercising. So I'm currently back
Jeff Clites <[EMAIL PROTECTED]> wrote:
> On Mac OS X, the test below is failing.
s/Mac OS X/Everywhere/
> initialization order is incorrect (at least, doesn't match what the
> test is expecting, and doesn't match what you'd want based on the
> diagram in the test)--init on D is called before ini
At 10:54 AM +0200 4/7/04, Leopold Toetsch wrote:
Jens Rieks <[EMAIL PROTECTED]> wrote:
Can I get commit privs?
That would be the best.
I'm fine with it too. Set up a perl.org account (pointers to it from
bugs.perl.org) and mail me your login and I'll get things in motion.
--
At 10:24 AM +0200 4/7/04, Leopold Toetsch wrote:
I'd like to separate functions of interpreter.c into distinct files
(it's currently more then 2500 lines):
init ... init destroy
cb ... callback function handling
run_loop ... runloop selection
run_fromc ... call runloop from c
load_ops ... dyna
Here's something for someone who wants to dig in a bit and needs a
place to start.
Many, but by no means all, of the ops are JITted right now. There's
code to mess about with the JITting in jit2h.pl. What would be nice
is if there was a way to get a list of the ops that are *not* JITted,
so it
At 8:50 AM +0200 4/7/04, Leopold Toetsch wrote:
We still have two locations for runtime stuff:
- runtime/parrot/*/
- library/
Let's move everything to runtime/parrot
1) We should probably decide to use just one for simplicity.
2) Library search paths and appropriate helper functions inside
Parrot
On Wednesday 07 April 2004 21:57, Dan Sugalski wrote:
> At 8:50 AM +0200 4/7/04, Leopold Toetsch wrote:
> >We still have two locations for runtime stuff:
> >- runtime/parrot/*/
> >- library/
>
> Let's move everything to runtime/parrot
I can take care of it when I have checkin access.
> >1) We shou
Update to this patch -
Jerome has identified an issue with the language testing patch - turns
out that perl6's test suite has carnal knowledge about Parrot::Test.
One of the changes I made to Parrot::Test broke the perl6 test suite.
The following bits of the Parrot::Test patch need to be revers
Andy, etal,
Id like to propose that I (or someone like me) add a passthru option
which lets someone pass thru options and arguments to the test scripts
being run.
The idea is to support 'torture' testing as it is typically (I think)
done now.
and not coincidentally ...
[EMAIL PROTECTED] added
> Id like to propose that I (or someone like me) add a passthru option
> which lets someone pass thru options and arguments to the test scripts
> being run.
Is this better than some kind of environment variable that you set, and
that your test programs detect and use?
xoa
--
Andy Lester => [EM
Andy Lester wrote:
Id like to propose that I (or someone like me) add a passthru option
which lets someone pass thru options and arguments to the test scripts
being run.
Is this better than some kind of environment variable that you set, and
that your test programs detect and use?
xoa
th
> thats precisely what -v does currently, same convenience argument applies.
I see a difference in that
prove -v
is shorthand for
TEST_VERBOSE=1 make test
I'm not against the idea. Just not sure about the implementation.
Whyncha write the manpage docs for how it'll work? That'll
Andy Lester wrote:
thats precisely what -v does currently, same convenience argument applies.
I see a difference in that
prove -v
is shorthand for
TEST_VERBOSE=1 make test
I thought it was
"HARNESS_VERBOSE"
If true, Test::Harness will output the verbose results
36 matches
Mail list logo
