cvs commit: ponie README

cvsuser     04/07/21 02:45:40

  Modified:    .        README
  Log:
  
  
  Revision  Changes    Path
  1.3       +41 -13    ponie/README
  
  Index: README
  ===================================================================
  RCS file: /cvs/public/ponie/README,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -w -r1.2 -r1.3
  --- README	12 Mar 2004 15:40:30 -0000	1.2
  +++ README	21 Jul 2004 09:45:39 -0000	1.3
  @@ -1,22 +1,50 @@
  -
  -This is Ponie, development release 2
  +This is Ponie, development release 3
   ------------------------------------
   
  -	"And, isn't sanity really just a one-trick ponie anyway? I mean all you get is one trick, rational thinking, but when you're good and crazy, oooh, oooh, oooh, the sky is the limit." -- the tick
  -
  -
  -Welcome to this second development release of ponie, the mix of perl5 and parrot. Ponie embeds a parrot interpreter inside perl5 and hands off tasks to it, the goal of the project is to hand of all data and bytecode handling to parrot.
  -
  -With this release all internal macros that poke at perl data types are converted to be real C functions and to check if they are dealing with traditional perl data types or PMC (Parrot data types) data. Perl lvalues, arrays and hashes are also hidden inside PMCs but still access their core data using traditional macros. The goal and purpose of this release is to make sure this approach keeps on working with the XS modules available on CPAN and to let people test with their own source code. No changes where made to any of the core XS modules.
  -
  -This is based on perl 5.9.1 as it existed in September, when 5.9.1 is really released ponie will be updated to that version, this might lead to there being perl bugs in ponie that are fixed in later versions on ponie.
  -
  -If you embed perl, nothing should have changed but parrot takes control over a substantial part of the interface to the operating system, this might cause problems for you. (One example is that parrot seems to hijack SIGINT currently, and weird issues with STDERR).
  +    "And, isn't sanity really just a one-trick ponie anyway? I mean all you
  +    get is one trick, rational thinking, but when you're good and crazy,
  +    oooh, oooh, oooh, the sky is the limit." -- the tick
  +
  +
  +Welcome to this third development release of ponie, the mix of perl5 and
  +parrot. Ponie embeds a parrot interpreter inside perl5 and hands off tasks to
  +it, the goal of the project is to hand of all data and bytecode handling to
  +parrot.
  +
  +With this release the C type of the perl core's data pointer, SV *, is actually
  +PMC *, the C type of parrot's data pointer. The functions emulating the macros
  +perl traditionally used to access its data structures now retrieve data from the
  +parrot PMCs. Some values are now retrieved and set via parrot's keyed lookup
  +methods in the PMC vtable. Other values are now intentionally stored in other
  +locations - the integer and floating point values (IVX and NVX) are now moved to
  +the SV head structure, and any references are pointed to from the core parrot
  +PMC structure, rather than sharing the space used by perl's PVX pointer. The
  +latter change will allow parrot to directly track perl references with its dead
  +object detection routines, once the switch is made from perl's reference
  +counting to parrot's garbage collection. All this has been hidded by changing
  +just the functions emulating perl's access macros - there has been no need to
  +change any other part of the core code, or the core's XS modules.
  +
  +The purpose of this release is to make sure this approach keeps on working with
  +the XS modules available on CPAN and to let people test with their own source
  +code.
  +
  +This is based on perl 5.9.1 as released in March, so will contain all core perl
  +bugs still present in that release. When 5.9.2 is released ponie will be
  +updated to that version.
  +
  +If you embed perl, nothing should have changed but parrot takes control over a
  +substantial part of the interface to the operating system, this might cause
  +problems for you. (One example is that parrot seems to hijack SIGINT currently,
  +and weird issues with STDERR).
   
   INSTRUCTIONS
   ------------
   
  -run Configure.pl using your own perl, this will Configure perl, then configure parrot, build parrot and reconfigure perl with all the correct settings. If you run into a problem here, you can try doing this manually.
  +Run Configure.pl using your own perl. This will Configure perl, then configure
  +parrot, and then tweak the perl configuration with settings from parrot. If you
  +run into a problem here, you can try doing this manually. Any arguments you
  +pass to Configure.pl will be passed on to parrot's Configure.pl
   
   After this just do make; make test and all tests should pass!