Re: call_back() etc
On Thu, 12 Aug 1999, Kat wrote:
> One word: huristics.
>
> I expect i will not know when i write more code that i will know all i want
> the code to do, indeed, i expect the code to write more of it's own code. I
> fully expect and hope that new vars will be created, var names that i can
> only guess at now, altho i do have a skeleton for it to build on. I, for
> one, will need the code i write to be able to interface to code i have no
> knowledge of, using variables i don't know the names of. So far, what i have
> done does work, and i hope it works in Eu. This is why i wish to avoid *all*
> type checking also, i have no idea what the types are, and i don't care
> either. If a variable is a math expression, maybe i want to *execute* that
> variable, if it is an integer, then i can increment it, or maybe i want to
> append them and print them out. I do not want info types locked in at
> compile time or at run time. If i have a callable function that does
> something, and i want it to do something new *while the calling app is
> running*, because the program learned something and wants to implement it,
> then it should be free to do so. It's the basic principle of learning, to
> grow, to be able to do things not known at compile time.
Interesting. What answer (or answers) will your program give to this question:
what is "Hello World" + 29.95 ?
Irv
|
Not Categorized, Please Help
|
|
