Clinton Pierce wrote:
Clarification:
running an invoke() at *any* time will cause all subsequent tracing to segfault.
I can't reproduce that on Linux (even with Dan's patch not applied yet).
leo
Clinton A. Pierce (via RT) wrote:
Suggestions welcome!
First, always check the result of IO operations. If something fails,
these return a PerlUndef, so:
.sub _main
fdopen $P1, 0, r # STDIN
defined $I0, $P1
unless $I0, err
read $S0, $P1, 255
print $S0
Some parrot opcodes like interpinfo, stringinfo, warnings{on,off} have
constant items as an argument selecting some action. These are well
documented and working fine, but rather unreadable in PASM/PIR source
code and are suboptimal if some item ever needs a different value.
So I'd like to
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #22855]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=22855
Attached is a minimum patch to build imcc as the parrot executable
- renames
First, always check the result of IO operations. If something fails,
these return a PerlUndef, so:
.sub _main
fdopen $P1, 0, r # STDIN
defined $I0, $P1
*Doh* Stupid Newbie Error.
unless $I0, err
read $S0, $P1, 255
# New Ticket Created by Simon Glover
# Please include the string: [perl #22856]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=22856
With a fresh checkout, I get:
imcc.y:401: conflicting types for `YYSTYPE'
Simon Glover [EMAIL PROTECTED] wrote:
With a fresh checkout, I get:
imcc.y:401: conflicting types for `YYSTYPE'
imcparser.h:6: previous declaration of `YYSTYPE'
/usr/lib/bison.simple: In function `yyparse':
/usr/lib/bison.simple:432: warning: passing arg 1 of `yylex' from
incompatible
Clinton Pierce [EMAIL PROTECTED] wrote:
.sub _main
fdopen $P1, 0, r # STDIN
BTW
fdopen $P1, 0, # read STDIN
3. its currently only defined for PIO_OS_UNIX
Okaaay, so the plan is for this to work and I should probably code this way anyway,
right?
# New Ticket Created by Simon Glover
# Please include the string: [perl #22857]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=22857
Hi,
I'm getting failures in tests 1 2 in t/pmc/io.t; however, both tests
seem
On Mon, 30 Jun 2003, Leopold Toetsch wrote:
Simon Glover [EMAIL PROTECTED] wrote:
With a fresh checkout, I get:
imcc.y:401: conflicting types for `YYSTYPE'
imcparser.h:6: previous declaration of `YYSTYPE'
/usr/lib/bison.simple: In function `yyparse':
/usr/lib/bison.simple:432:
A further data point: the tests pass if I use IMCC to assemble them,
rather than assemble.pl
Simon
On Wednesday 25 June 2003 20:15, Adrian Howard wrote:
Add an explicit test script finished footer?
But how does the footer-adder know that the correct number of tests ran. You
would need to declare a plan to run x additional extensions at which point
you're doing sub-plans.
I suppose I'm
Dave Whipp wrote:
Matt Fowles
Were this C++ I would say that we could write a single general
purpose stack and use template meta-programming to avoid the
overhead. Is there a similar solution available in C?
My instincts tell me that this solution will be dirty to the tune of
massive
Brent Dax wrote:
Benjamin Goldberg:
# Concievably, we could then examine the exception, and maybe decide
# that it was nonfatal, and resume execution from just after the place
# it was thrown from.
The problem with that is that some exceptions are unresumable. For
example, exceptions
Leopold Toetsch [EMAIL PROTECTED] writes:
Dan Sugalski [EMAIL PROTECTED] wrote:
Exception handlers really strike me as anonymous lexically scoped
subroutines that get called with just one parameter--the exception
object. As far as the engine should be concerned, when an exception
is taken we
Simon Glover [EMAIL PROTECTED] wrote:
I'm getting failures in tests 1 2 in t/pmc/io.t; however, both tests
seem to run fine if I run them in the debugger.
valgrind does indicate, that there are unitialized items in many
parts of io_buf.c.
(I don't know, if these tests even should use the
At 11:53 AM -0400 6/30/03, Benjamin Goldberg wrote:
Brent Dax wrote:
Benjamin Goldberg:
# Concievably, we could then examine the exception, and maybe decide
# that it was nonfatal, and resume execution from just after the place
# it was thrown from.
The problem with that is that some
Hi all,
I've settled on Test::NoWarnings as the right name for this.
This improves on Test::Warn 0.02 by
- not running the test in forked children
- capturing the warnings as objects
which is to say that for most people, it's exactly the same.
F
On Mon, 30 Jun 2003, Leopold Toetsch wrote:
Attached is a minimum patch to build imcc as the parrot executable
Please give it a try on other platforms, especially non Linux.
Sun's make failed with the following error:
make: Fatal error: Don't know how to make target `languages/imcc/*.o'
Dan Sugalski [EMAIL PROTECTED] writes:
At 11:19 PM +0200 6/29/03, Leopold Toetsch wrote:
Dan Sugalski wrote:
... I'd also like to be able to manipulate the stacks in a context,
pushing things on them, changing values on them, and generally
messing about with the things, so I'm all for it.
The Perl 6 Summary for the week ending 20030629
Welcome to the third of my US tour Perl 6 summaries. Once again I'm
pleased to report that the denizens of the Perl 6 mailing lists continue
to make the life of a touring summarizer an easy one by not posting all
that much to the
Piers Cawley wrote:
Small Perl task for the interested
Want to get involved in the Parrot development process? Don't know much
about Virtual Machine design and implementation? Do know Perl? Dan has a
small but interesting task for you.
At present, Parrot gets built without any
Alan Burlison wrote in perl.perl6.internals :
Piers Cawley wrote:
Small Perl task for the interested
Want to get involved in the Parrot development process? Don't know much
about Virtual Machine design and implementation? Do know Perl? Dan has a
small but interesting task for
Rafael Garcia-Suarez wrote:
Hmm, I'm only a lurker, but that looks *very* suspect to me. Some compilers
may choose to reorder even without optimization turned on. I'd say that it
is a bug in Parrot if it requires optimization to be off for this code - how
many different compilers have you
Clinton Pierce [EMAIL PROTECTED] wrote:
I checked in a fix for something that *may* have fixed this, but I'm
not sure as I can't test it out at the moment. Try sync'ing up to CVS
and giving it another whirl.
Still no luck. No luck either in getting a stack trace to the problem.
This may
Andy Dougherty [EMAIL PROTECTED] wrote:
On Mon, 30 Jun 2003, Leopold Toetsch wrote:
Attached is a minimum patch to build imcc as the parrot executable
languages/imcc/*.o
languages/imcc/*.o doesn't match anything
Brain dead make? Anyway, this line could for sure be deleted.
26 matches
Mail list logo
