On Tuesday, October 20, 2015 at 4:25:00 PM UTC-7, Anthony wrote: > > Determining at runtime that a particular function exists seems expensive >> if you have control over the source file that defines the target and the >> function that needs to know. >> > > I don't see why it would be particularly expensive -- just a dictionary > lookup. We already have code like "if something in globals():" in some > places in the scaffolding app. > > Anyway, in the non-dynamic case, I'm not sure what role source control > would play. If you're making a fixed function call, you should simply know > what functions are available in your codebase (of course, there are various > IDE tools that can help identify all the available functions if you don't > have proper documentation or want to browse the source code). >
Source control is just making sure that the rev of the file is the one with the definition and the usage. Overly verbose version: Many of us use source control in a pretty monotonic fashion ... just archiving the changes as we go along ... and I wouldn't expect most people to have an issue adding functions along the way, but some people have to support multiple versions, or to backdate something to analyze when and how a bug was introduced, and source control will make sure the new function's definition and its usage are in sync across those versions. /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
