bruno at modulix <[EMAIL PROTECTED]> writes: > Burton Samograd wrote: > > "infidel" <[EMAIL PROTECTED]> writes: > > I'm a C programmer, so I'm doing it in a bit of a C like way; > > prototype the function, initalize the array using the prototypes, have > > the functions defined somewhere else and then let the linker work it > > all out for me. I was hoping that python had some sort of lazy > > evaluation scheme for this type of behaviour so that you could defer > > linkage (or variable evalutation) until runtime, or at least variable > > reference (through the use of thunks or some sort). Maybe I was > > hoping for too much :) > > It's not a problem of "hoping for too much", but a problem of paradigm > shift. You're actually *thinking* in C, and Python is a *completely > different* language. You just can't directly transpose C idioms in > Python - nor could you transpose much Python idioms in C. So you need to > 'go down a level' and consider the real problem and how to solve it the > Python way - not how to implement the C-ish solution in Python.
To be honest, I'm trying to do it in a more 'lispish' way (as in emacs lisp) where the configuration file is written in the implementation langugage. Just an interesting experiement really to see if it would work. It's been a year and a half since I really used python last so I'm just getting back up to speed with the idioms so I expect to make a few mistakes along the way. Thanks for the help. -- burton samograd kruhft .at. gmail kruhft.blogspot.com www.myspace.com/kruhft metashell.blogspot.com -- http://mail.python.org/mailman/listinfo/python-list
