Slightly cleaner patch than the crude method of cat'ing the ops files
into one .ops file.
Also doesn't require patching all the places dependent upon 'core'.
-Jeff
<[EMAIL PROTECTED]>
---cut here---
diff -ru parrot_orig/Makefile.in parrot/Makefile.in
--- parrot_orig/Makefile.in Thu Nov 22 16
Rather wordy, I know, but it also points out how many places depend upon
the name 'core' in the current code.
I'm also posting a different version shortly that combines core.ops and
vtable.ops into one core_ops.{c,h,pm}.
-Jeff
<[EMAIL PROTECTED]>
--- cut here ---
diff -ru parrot_orig/Configure.
I was wandering around looking for some non-parrot related stuff, and came
across this wonderful tidbit. Was this mentioned somewhere in the mail list
or on perl.com and I missed it?
http://www.unixreview.com/documents/s=1780/urm0111h/0111h.htm
If it wasn't posted to the prl6-* list, it should be
I suppose some of you will have noticed that Parrot development took
quite a bit of a shot in the arm last Thursday and Friday. Over 150k of
source commits happened, and integer PMCs, interpreter spawning and a
bunch of vtable documentation sprung into being.
This is due directly to the generosit
This is cool shit, but I'd like you to give it another going
over in the light of my last commit. This allows you to say
new P0, 0
and have a new Perl-integer-like PMC in register 0. Together with
vtable.ops, if that's linked in, it should now be possible to
perform operations on integer PM
All right, inserting the file *inline* this time...
*grumble*grumble*Netscape*grumble*firewall*grumble*
In any case, the file is now known to be below these comments.
As noted previously, many of these tests should actually return
something (an error string, or maybe an actual numeric value or s
