in reply to Sharing globs

Cloning requires copying. Sharing requires locking and triggers on any updates so the updates get applied to the other thread(s). Clearly, nobody has yet written the code to put all of the locking and triggers in place for globs.

Now, there certainly could be more to it than that. But I can certainly understand writing the code to lock and trigger for scalars before writing the code to lock and trigger for globs (since that code for globs isn't of much use if you don't have the code for all of the items contained in a glob already anyway).

- tye        

Replies are listed 'Best First'.
Re^2: Sharing globs (tuits)
by BrowserUk (Patriarch) on Oct 27, 2007 at 16:49 UTC

    Well yeah, but that doesn't help me work out what needs to be done to change it. I can see and disable all the checks that prevent it, but (unsurprisingly) the results segfault. Sometimes.

    So I'm trying to understand the technical reasons why it hasn't been done before now--not the social ones.


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.