Well, threads have their own namestack, but they share the global namespace. You can write code using only set-global and get-global where threads wouldn't interact well, but if you use with-scope around code that modifies variables, there should be no need to worry about interaction between threads. There's no way to absolutely prevent other code from using set-global on your variable, but you can make the delimiter variable private to indicate that it shouldn't be messed with.
Dan On Wed, Jul 30, 2008 at 3:18 AM, Phil Dawes <[EMAIL PROTECTED]> wrote: > Cool thanks. Just so I'm sure, does each thread have it's own complete > namestack? E.g. so thread 'b' can't override thread 'a's delimiter at > the root namespace halfway through a csv import? > > Cheers, > > Phil ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
