bug-kawa
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-kawa] [bug #33325] using setIndirectDefines safely


From: Per Bothner
Subject: [Bug-kawa] [bug #33325] using setIndirectDefines safely
Date: Mon, 16 May 2011 19:52:55 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24

Update of bug #33325 (project kawa):

                  Status:                    None => Need Info              
             Assigned to:                    None => bothner                

    _______________________________________________________

Follow-up Comment #1:

This does not seem like the right solution.  Setting a static flag to control
behavior usually isn't.  (I know there are a number of these in Kawa, but I
don't like it, and in any case most of these are set as defaults from the Kawa
command line, where setting global state might be tolerable.)

So the obvious question is: Why is setIndirectDefines called too late?  Would
it be possible to call Environment.make (followed by Environment.setCurrent)
explicitly and early when the thread is created?  Or perhaps add a new
Environment.makeShared factory method?

If we really need a global flag, it might be cleaner to use a 
gnu.mapping.ThreadLocation (which is what Scheme's make-parameter is built
on).

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?33325>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]