At 11:23 PM 10/10/2003 +0100, Nicholas Clark wrote:
On Fri, Oct 10, 2003 at 05:55:11PM -0400, Melvin Smith wrote:
> Which ones? The PIOCTL ones are, for a lack of current
> interface, a way for interfacing to the lower level IO
> system through a catchall opcode. It can be anything from
> setting t
# New Ticket Created by "Adam Thomason"
# Please include the string: [perl #24185]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=24185 >
Here's the beginning of support for debugging the JIT core with the native compiler o
On Fri, Oct 10, 2003 at 05:44:05PM +0200, Leopold Toetsch wrote:
> Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > On Fri, 10 Oct 2003, Leopold Toetsch wrote:
>
> >> - the opcode numbers are assigned dynamically:
> >> When you load an oplib containing 100 ops, they get op numbers
> >> e.g. 1206 ..
the top level Makefile has this rule to build the object files in
languages/imcc:
$(IMCC_DIR)/%.o : $(IMCC_DIR)/%.c
$(PERL) tools/dev/cc_flags.pl ./CFLAGS $(CC) -I$(IMCC_DIR) $(CFLAGS) -o $@ -c
$<
the build fails at imcparser.o for me (the first object file)
Running make with some debug
On Fri, Oct 10, 2003 at 05:55:11PM -0400, Melvin Smith wrote:
> Which ones? The PIOCTL ones are, for a lack of current
> interface, a way for interfacing to the lower level IO
> system through a catchall opcode. It can be anything from
> setting terminal modes, buffering, separator characters, the
Which ones? The PIOCTL ones are, for a lack of current
interface, a way for interfacing to the lower level IO
system through a catchall opcode. It can be anything from
setting terminal modes, buffering, separator characters, the
list goes on.
Although we probably want to make separate ops for
commo
At 07:01 PM 10/10/2003 +0200, Juergen Boemmels wrote:
Hi,
I'm currently working on some bugs in the PIO_seek code, and i find
the current return-code of Seek impractical: it just returns 0 on
success and -1 on error. I found myself writing code like
PIO_seek_down(...);
pos = PIO_tell_down(...);
bu
The tinders are complaining about missing dynoplibs/Makefile. While I'm
not sure we should ultimately have a static makefile anywhere, I'm pretty
sure that if we *do* have one mentioned in the Manifest that it ought to
be in the repository... :)
Dan
On Fri, Oct 10, 2003 at 12:35:23PM +0200, Leopold Toetsch wrote:
> Nicholas Clark <[EMAIL PROTECTED]> wrote:
>
> > I'm having trouble testing this because I can't get CVS parrot to build on
> > my (friend's) freebsd box. I think that this ought to restore 5.005_03
> > compatibility:
>
> parrot bu
Hi,
I'm currently working on some bugs in the PIO_seek code, and i find
the current return-code of Seek impractical: it just returns 0 on
success and -1 on error. I found myself writing code like
PIO_seek_down(...);
pos = PIO_tell_down(...);
but in the layer implementations typically is this cod
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> On Fri, 10 Oct 2003, Leopold Toetsch wrote:
>> - the opcode numbers are assigned dynamically:
>> When you load an oplib containing 100 ops, they get op numbers
>> e.g. 1206 ... 1305. Next oplib starts at 1306 ...
>> - on load all runcores are notified
On Fri, Oct 10, 2003 at 02:43:10AM -, Melvin Smith wrote:
> +else if(arg == PIOCTL_BLKBUF) {
> + PIO_setbuf(interpreter, pmc, PIO_UNBOUND);
> + return 0;
> +}
> +else return -3;
> case PIOCTL_CMDGETBUFSIZE:
>
On Fri, 10 Oct 2003, Leopold Toetsch wrote:
> - the opcode numbers are assigned dynamically:
> When you load an oplib containing 100 ops, they get op numbers
> e.g. 1206 ... 1305. Next oplib starts at 1306 ...
> - on load all runcores are notified to use the new oplib function
> or address t
On Friday, Oct 10, 2003, at 14:22 Europe/Berlin, Dan Sugalski wrote:
On Fri, 10 Oct 2003, Leopold Toetsch wrote:
Michael Scott <[EMAIL PROTECTED]> wrote:
config/gen/platform/darwin.c
Add conditional code for PARROT_HAS_HEADER_DLFCN.
Could you please rediff the patch w/o the whitespace cha
Hi,
I just removed the PutS and GetS functions PIOLayerAPI. This
API-functions used plain C-Strings and had no advantage over the Read
and Write API-calls. They just introduced a second code-path. The only
function actually using this API was PIO_puts, which was easily
changed to use the Write API
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Right now there's a load_pmc op, which goes along with the load_opcode_lib
> and loadlib ops. I'd like to unify that
I'll start the opcode load thingy, based on my experimental code I has
posted here mid-March.
The basics are:
- assembler and runtime mus
At 08:31 AM 10/10/2003 -0400, Dan Sugalski wrote:
On Thu, 9 Oct 2003, Melvin Smith wrote:
> Added pioctl op and PIO_pioctl API call. General purpose op for IO
manipulation
> in tradition of UNIX ioctl call.
>
> This will be the interface for doing all sorts of IO layer stuff such as
> buffering,
On Thu, 9 Oct 2003, Melvin Smith wrote:
> I fixed a bug in the readline routine that now allows it to act
> like it should. With the ability to toggle linebuffering on IO
> handles now with pioctl, do we need the explicit readline op
> anymore?
If it's identical to a read now, then no. We might w
On Thu, 9 Oct 2003, Melvin Smith wrote:
> Added pioctl op and PIO_pioctl API call. General purpose op for IO manipulation
> in tradition of UNIX ioctl call.
>
> This will be the interface for doing all sorts of IO layer stuff such as
> buffering, blocking, async, etc. At least until someone has a
On Thu, 9 Oct 2003, Thomas Fjellstrom wrote:
> On October 9, 2003 09:57 am, Dan Sugalski wrote:
> > On Thu, 9 Oct 2003, Dave Mitchell wrote:
> > > On Thu, Oct 09, 2003 at 11:43:41AM -0400, Dan Sugalski wrote:
> > > > We've got ordered destruction on the big list 'o things to do, and it
> > > > loo
On Fri, 10 Oct 2003, Leopold Toetsch wrote:
> Michael Scott <[EMAIL PROTECTED]> wrote:
> > config/gen/platform/darwin.c
> > Add conditional code for PARROT_HAS_HEADER_DLFCN.
>
> Could you please rediff the patch w/o the whitespace changes. An indent
> of 4 is ok, you seem to have 8 in place.
On Fri, 10 Oct 2003, Leopold Toetsch wrote:
> Dan Sugalski <[EMAIL PROTECTED]> wrote:
>
> > No. If any object has a destructor it should be called as the last
> > interpreter is shut down. We're not guaranteeing dead-on immediate
> > destruction, or if the timely flag isn't set timely destruction,
Nicholas Clark <[EMAIL PROTECTED]> wrote:
> I'm having trouble testing this because I can't get CVS parrot to build on
> my (friend's) freebsd box. I think that this ought to restore 5.005_03
> compatibility:
parrot builds and tests fine here with 5.005_03
$ perl5.00503 -V
Summary of my perl5 (5
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Dan Sugalski <[EMAIL PROTECTED]> wrote:
>
> > No. If any object has a destructor it should be called as the last
> > interpreter is shut down. We're not guaranteeing dead-on immediate
> > destruction, or if the timely flag isn't set timely destruction
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Juergen Boemmels <[EMAIL PROTECTED]> wrote:
>
> > It turned out, that it was even simpler. The explicit sweeping is
> > already in the code, but is only triggered if there are objects which
> > need _early_ destruction, not if objects just need
> > de
Peter Sinnott <[EMAIL PROTECTED]> wrote:
> A proposed freebsd hint file is attached( a copy of the current aix
> hint file )
Thanks applied.
leo
Michael Scott <[EMAIL PROTECTED]> wrote:
> config/gen/platform/darwin.c
> Add conditional code for PARROT_HAS_HEADER_DLFCN.
Could you please rediff the patch w/o the whitespace changes. An indent
of 4 is ok, you seem to have 8 in place.
Thanks.
leo
27 matches
Mail list logo
