Wouldn’t that depend on how the table is referred to?
For instance, if a table is referred to by name rather than a memory location then creating a new version and copying all that stays the same works fine. I created just such code and it worked for more than 30,000 customers. I currently am creating exactly this kind of code. Even in memory, I make no references that are just a pointer for exactly the reason you suggest. The references I create can change physical location in memory without breaking any code. David From: Russell Wallace [mailto:[email protected]] Sent: September-11-13 8:12 PM To: AGI Subject: Re: [agi] Module re-definitions If ( exists(table(A))) then drop table A ; Create table A as blah blah blah... ee? no! that would break everything that refers to table A. modify it in place instead. In 3 GL languages like C++, Java, etc. when a code module is accidentally included twice in a source file, what exactly happens? Does the compiler redefine or ignore the functions or objects in the duplicate module? What about interpreted languages like python? what you want is usually that importing a module is idempotent, i.e. doing it twice is the same as doing it once. The mechanisms by which this is achieved are very different in C++ versus Java but it is achieved nonetheless. AGI | <https://www.listbox.com/member/archive/303/=now> Archives <https://www.listbox.com/member/archive/rss/303/1652298-7c98969f> Image removed by sender.| <https://www.listbox.com/member/?&;> Modify Your Subscription <http://www.listbox.com> Image removed by sender. ------------------------------------------- AGI Archives: https://www.listbox.com/member/archive/303/=now RSS Feed: https://www.listbox.com/member/archive/rss/303/21088071-f452e424 Modify Your Subscription: https://www.listbox.com/member/?member_id=21088071&id_secret=21088071-58d57657 Powered by Listbox: http://www.listbox.com
<<~WRD000.jpg>>
