Re: $?OS semantics

2008-01-07 Thread Larry Wall
On Mon, Jan 07, 2008 at 02:05:18PM -0500, Trey Harris wrote: > And mix the role in to $*OS. Then call $*OS.trytolink() to get the proper > behavior at the proper time. Imagine a Beowulf cluster of those, and now $*OS might even point to thread-specific data. Larry

Re: $?OS semantics

2008-01-07 Thread chromatic
On Monday 07 January 2008 08:42:06 Trey Harris wrote: > Then we can have roles that describe cross-cutting behavior of various > OS's (like POSIX): > >    my &trytolink; >    give $?OS { >       when OS::HasSymlinks { &trytolink := &*symlink; } >       when OS::HasLinks    { &trytolink := &*link;

Re: $?OS semantics

2008-01-07 Thread Trey Harris
In a message dated Mon, 7 Jan 2008, Larry Wall writes: On Mon, Jan 07, 2008 at 11:42:06AM -0500, Trey Harris wrote: So $?OS isn't "the type of OS", it's *the OS*, and you can manipulate the OS through it. Note that $?OS is the OS that is-or-was running at compile time, whereas $*OS is the OS r

Re: $?OS semantics

2008-01-07 Thread Larry Wall
On Mon, Jan 07, 2008 at 11:42:06AM -0500, Trey Harris wrote: > So $?OS isn't "the type of OS", it's *the OS*, and you can manipulate the > OS through it. Note that $?OS is the OS that is-or-was running at compile time, whereas $*OS is the OS running right now (at run time). Those don't have to b