Re: Functions for embedders to override

Dan Sugalski wrote:

> Since we're running into Ponie issues with this, which means we'll run 
> into Apache issues as well as any number of other systems....
> 
> When Parrot's being embedded I can see the following functions needing 
> overriding by the embedder:
> 
> *) Memory: malloc, realloc, calloc, free
> *) Signals: handler register, Handler un-register, signal raise, alarm set
> *) Files: Open, close, seek, tell, read, write. (Possibly asynchronously)

   *) Environment: getenv, setenv
   *) Threading/Process manipulation? (fork, spawn, wait, pthread_*) (Consider
      an application built on a runtime that expects to know about all threads
      in a process, or an embedder who wants to let their Parrot programs call
      back into the main program or integrate into their main event loop.)
   * Networking: socket, accept, connect, listen, etc. (see "Files")

A good place to look at for the complete list is Perl 5's system abstraction
layer.

-- BKS