Am 14.02.2007 um 18:03 schrieb Matt Good: > Elixir is using functions that behave similarly to Trac's implements() > to modify the class declaration where they're used and someone > mentioned that using a global to handle this is not thread-safe, > unlike the frame-inspection method formerly used by Trac: > http://groups.google.com/group/sqlelixir/browse_thread/thread/ > 1fb0b9512ad29fd1/a2d4e5ae55e11104?#a2d4e5ae55e11104 > > This is where Trac's implementation was changed: http:// > trac.edgewall.org/changeset/3729 > > I don't know of any problems that have actually occurred because of > this, but if there's a chance this could happen, I guess it's better > to be safe.
Good point. The inner class example is pretty convincing, regardless of whether there's a thread-safety problem lurking here. I'd be okay switching back to the frame hacking. BTW, the idea for the change in r3729 was based on comments on <http://blog.ianbicking.org/more-on-python-metaprogramming.html>. Cheers, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
