On Fri, May 22, 2009 at 2:00 PM, Nick Alexander <ncalexan...@gmail.com> wrote: > >> We do this to avoid the (large) overhead of re-creating constants in >> the bodies of loops, functions, etc. Perhaps we need to detect the >> Integer=xxx line explicitly? > > Doing this accurately is equivalent to the halting problem. This is > what pragmas are for, but do we really want to start supporting all > these compiler features? When is sage no longer python?
Another possibility, which is much easier than the halting problem :) and would fix at least this issue, is to put the constant-creation code just before the top-level statement that uses the constant. (So if method in a class uses a constant, I'm proposing to put the constant creation just before the class.) Carl --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
