CompuServe Messages

Well yes Tony I do understand dynamic binding and the only way to settle such a debate is by bringing in computer science. But I'll try not to. What we are talking about is can a executable grow or modify it's own code. Well with 'C' or assembly language I can accomplish such a task. I am currently in the process of writing such a program. It incorporates a builtin compiler that translates psuedo-code into machine code. But does a AutoLISP program truly grow? It's storage space can vary, just like any executable. Are you talking about when a AutoLISP program creates a list that it can (eval). Well that isn't dynamic binding in my book. When execution of the running AutoLISP process ends, those lists are lost. If AutoLISP was reentrant, then it would be doing a form of dynamic binding. My program will accomplish such a task, using C++. Virus's accomplish dynamic binding regularly, as well as some TSR's. Even the process of overlay management could be described as dynamic binding. In other words, the size of the executable changes according to the current events in process. Ted PS Yes I overuse the (therefor <assertion>).