Re: Parrot hijacks SIGINT

Dan Sugalski wrote:
> At 5:27 PM +0000 3/15/04, Arthur Bergman wrote:
>> No it doesn't, because an embedding environment might not want to let 
>> parrot deal with signals, ever, and it might feel to restrict when it 
>> sends them off. Signals are an environment issue and thus should be 
>> controlled from the host app.
> 
> Yeah. We're ultimately going to have to add signals to memory allocation 
> and IO as things that the embedding environment controls.

Is it just me, or does this sound awful similar to the existing list of 
platform-dependent code?  Does this suggest that we should be looking at 
having the platform functions pluggable at runtime?  (IE by making a 
vtable out of them, and making that vtable swappable at runtime... or 
just making them a full-blown ParrotSystem object out of them, though 
that may raise "interesting" circular problems.)

(Yes, I do need to do a fresh look at that section of code.)

	-=- James Mastros