Hey all.
I've noticed that we don't seem to have the concept of RAM. I see how it
could be emulated fairly easily, by creating a pad with one-byte PMCs,
though PMCs have to have string registers as their names, rather then
numbers. Is this a feature (IE PMCs names have to have names that are v
On 15 Oct 2001, Brian Wheeler wrote:
> With the addition of clone, I started writing some generic routines
> which might be useful (index,lc,uc,reverse,abs,tr,etc)...and I came
> across some weirdness:
>
> doing:
>save S0
>restore S1
>
> (since there's no set S1,S0)
>
> binds the regi
With the addition of clone, I started writing some generic routines
which might be useful (index,lc,uc,reverse,abs,tr,etc)...and I came
across some weirdness:
doing:
save S0
restore S1
(since there's no set S1,S0)
binds the registers together, so a change to one is a change to
both...whi
sys/time.h must be included for struct timeval for gettimeofday(). The current
CVS source is not compiling for me without this. Perl's Config module contains
a symbol for gettimeofday's availability, so it would be possible to make the
numeric time operator conditional on this define.
--
Jason
This patch replaces the existing CHUNK_BASE macro used for all the register
sets with separate (INT|NUM|STR|PMC)_CHUNK_BASE macros. The bit masks are
already determined by Configure thanks to Dan.
--
Jason
Index: Configure.pl
==
Fixes wayward copy and paste for register save ops:
RCS file: /home/perlcvs/parrot/core.ops,v
retrieving revision 1.4
diff -u -r1.4 core.ops
--- core.ops2001/10/15 21:18:42 1.4
+++ core.ops2001/10/16 01:40:34
@@ -1745,15 +1745,15 @@
}
AUTO_OP restore(n) {
- pop_generic_entry(in
At 07:24 PM 10/15/2001 -0500, Brian Wheeler wrote:
>Because I was bored this evening, I implemented the clone operators.
>
>Dan?
Looks, good. Thanks, and commit it! :)
Dan
--"it's like this"---
Dan Sugal
Because I was bored this evening, I implemented the clone operators.
Dan?
Brian
# compute the factorialrecursively!
# lets do it for the numbers 0 to 6
main:
set I1,0
$loop:
print "fact of "
print I1
print " is: "
set I0,I1
At 05:54 PM 10/15/2001 -0400, Jason Gloudon wrote:
>On Fri, Oct 12, 2001 at 11:16:55AM -0400, Dan Sugalski wrote:
>
> > Anyone care to throw together some tests for configure.pl to figure out
> the
> > *real* sizes for the register chunks (courtesy of a quick test program
> that
> > does some si
On Fri, Oct 12, 2001 at 11:16:55AM -0400, Dan Sugalski wrote:
> Anyone care to throw together some tests for configure.pl to figure out the
> *real* sizes for the register chunks (courtesy of a quick test program that
> does some sizeof() checks?) and figure out the power-of-two boundary these
Dan --
> >I've made core.ops contain op documentation, and I'd like to make it
> >the official place where ops are documented.
>
> Nope. :)
>
> parrot_opcodes.pod is essentially a design document. It's the documentation
> that describes the abstract machine that the code in the source implemen
Dan --
> >Agreed. But until we have those glorious libraries, I'm interested
> >in having those things we *do* have be as useful as possible.
>
> That's fine. I need to get in and start the loadable module code soon.
> After threads/interpreters and probably I/O, I think.
I'm interested in loa
On Mon, Oct 15, 2001 at 04:48:25PM -0400, Gregor N. Purdy wrote:
> + struct timeval t;
I don't think DOSalikes can handle gettimeofday.
--
Sendmail may be safely run set-user-id to root.
-- Eric Allman, "Sendmail Installation Guide"
At 05:16 PM 10/15/2001 -0400, Gregor N. Purdy wrote:
>Dan --
>
>I've made core.ops contain op documentation, and I'd like to make it
>the official place where ops are documented.
Nope. :)
parrot_opcodes.pod is essentially a design document. It's the documentation
that describes the abstract mac
Dan --
I've made core.ops contain op documentation, and I'd like to make it
the official place where ops are documented. That means I'd like to
make sure there is nothin documented in docs/parrot_assembly.pod that
isn't equivalently or superiorly documented in core.ops and then remove
the duplica
At 05:09 PM 10/15/2001 -0400, Gregor N. Purdy wrote:
> > The time opcode, though, like the print opcode, were really hacks in there
> > so I could show that *something* was happening in the interpreter, and
> > figure out how long that took. They were really toss-off opcodes that were
> > slated t
Dan --
> >Does anyone object to this going in? Can anyone give me info on
> >platform compatibility of this? Can we add some check to Configure.pl
> >to figure out what we can do?
>
> I don't have a problem with this.
OK. In it goes.
> The time opcode, though, like the print opcode, were reall
At 04:48 PM 10/15/2001 -0400, Gregor N. Purdy wrote:
>All --
>
>Does anyone object to this going in? Can anyone give me info on
>platform compatibility of this? Can we add some check to Configure.pl
>to figure out what we can do?
I don't have a problem with this.
The time opcode, though, like th
All --
Does anyone object to this going in? Can anyone give me info on
platform compatibility of this? Can we add some check to Configure.pl
to figure out what we can do?
Without objection, I'll commit soon.
Regards,
-- Gregor
_
In message <[EMAIL PROTECTED]>
Andy Dougherty <[EMAIL PROTECTED]> wrote:
> Yes, but they are empty, and there are no relevant entries in MANIFEST.
> Thus, if you try to make a copy of the parrot source tree in another
> directory based on the contents of the MANIFEST file, you'll get a
Back on Fri, 28 Sep 2001 20:49:42, Josh Wilmes <[EMAIL PROTECTED]> asked:
> What's the state of the coding standards? This is the last draft of it
> i've noticed in the archives:
>
> http://www.mail-archive.com/perl6-internals%40perl.org/msg03422.html
>
> Is this going to become a PDD or at
In perl.perl6.internals, you wrote:
>In message <[EMAIL PROTECTED]>
> Andy Dougherty <[EMAIL PROTECTED]> wrote:
>
>> ops2c and ops2pm need to make sure the directory for the output file
>> exists before trying to create any files in that directory.
>
>Well actually cvs should have created
> I'm about to start welding in support for multiple interpreters, running
> both serially and simultaneously, into Parrot. (With provisions for
> starting and coordinating interpreters from other interpreters)
>
> This is just a heads-up, since it probably means platforms without POSIX
> thread
At 12:25 PM 10/13/2001 -0400, Ryan O'Neil wrote:
>Thus spake "Dan Sugalski" <[EMAIL PROTECTED]>:
>
> > I'm not 100% sure I want random number generation to be a fundamental
> > part of the interpreter. (Though it *is* really appealing...) This sort
> > of thing might be better put in the standard
In message <[EMAIL PROTECTED]>
Andy Dougherty <[EMAIL PROTECTED]> wrote:
> ops2c and ops2pm need to make sure the directory for the output file
> exists before trying to create any files in that directory.
Well actually cvs should have created the directories when you
updated, so long
I'm about to start welding in support for multiple interpreters, running
both serially and simultaneously, into Parrot. (With provisions for
starting and coordinating interpreters from other interpreters)
This is just a heads-up, since it probably means platforms without POSIX
thread support w
Two patches inline...
A small change to Makefile.in so that 'make test' doesn't try to run without an
interpreter or missing assembler libraries.
Index: Makefile.in
===
RCS file: /home/perlcvs/parrot/Makefile.in,v
retrieving revisio
ops2c and ops2pm need to make sure the directory for the output file
exists before trying to create any files in that directory.
Also, I changed t/Makefile to use the correct $(PERL) version.
(But aren't those cd t; make ... commands going to give Win32 fits?)
diff -r -u parrot/Makefile.in parro
On Sun, Oct 14, 2001 at 10:21:06AM -0400, Jason Gloudon wrote:
>
>
> Patch for Configure.pl to create an empty vtable.h so that
> testparrotsizes will compile instead of running make, and to remove it once
> done.
Ignore this. I generated the patch on the wrong file. Some other folks
have poste
Should anything be changed?
--
H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/)
using perl-5.6.1, 5.7.2 & 629 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3,
WinNT 4, Win2K pro & WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED]
http:[EMAIL PROTECTED]/ [EMAIL PROTECTED]
send
30 matches
Mail list logo
