From: "Ben Goertzel" <[EMAIL PROTECTED]>
> A "hardware modality" -- perceiving registers, etc. -- seems to me like it
> should come AFTER a C++ - level codic modality.
>
> In other words, I advocate starting at the most abstract level -- with
> perception and action in the functional-language domain. Then imperative
> languages, beginning with perhaps Java or C#. Then C++. Then assembler,
> which comes along with the hardware modality. I don't think it's a good
> idea to start at the hardware level...
But why isn't it a good idea to start at the assembly level, the natural
language of the machine? High level languages, whether functional or
procedural or what have you are designed for human/programmer use. Even the
symbols used to program in assembly language are for human consumption, not
for computers.
One main problem I see with compiled programs is that in an executable
process there is generally a separation between code and data. I think that
code and data are actually one and the same, but it is useful to make the
separation for humans to write compilers. Wouldn't things be more simpler if
we understood how to program at the hardware (assembly) level with
self-modifying code? Can anyone recommend some good books?
Of course we should use existing frameworks with their possibly language
dependant API's for communication between computer systems or the host OS
and its devices. But the actual "business logic" of an AGI would/should be
implemented in a self-modifying machine code level.
cheers,
Simon
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?[EMAIL PROTECTED]
