"Ken Hagan" <[EMAIL PROTECTED]> writes: | I could write... | | int fk() { return k; } | | and re-cast my template to expect a pointer to function and then | write C<&fk>. This is perfectly legal under the current language | rules, and gives a type whose behaviour depends on the thread that | is using it.
This analgoy does not cut it: You don't have a function "fk" by thread. You have a -single- function designator. And the return value depends on the calling thread. -- Gaby _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost