On Mon, Nov 29, 2004 at 04:26:36AM -0000, Nigel Sandever wrote: > Ah but...that same POD also says: > > Note that if this module is imported when threads has not yet been > loaded, then these functions all become no-ops. This makes it possible > to > write modules that will work in both threaded and non-threaded > environments. > > In the absence of c<use threads>, threads::shared::share( ... ) becomes a > noop, > so what ever you put in comes out unchanged.
That's not how I read those docs, but regardless its incorrect for share() to return different things with threads on as opposed to off. > >Powered, not by a heart, but a sort of Wankel-Rotory Engine of Malevolence. > > Twice the malevolence per unit of swept volume relative to a reciprocating > equivalent huh? Hee. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/ Keep your stick on the ice. -- Red Green
