On Fri, Oct 24, 2008 at 6:39 PM, Russell Wallace <[EMAIL PROTECTED]> wrote: > On Fri, Oct 24, 2008 at 3:24 PM, Vladimir Nesov <[EMAIL PROTECTED]> wrote: >> Again, specifics. What is this "specification" thing? What kind of >> task are to be specified in it? Where does it lead, where does it end? > > At the low end, you could look at some of the fitness functions that > have been written for genetic programming. Moving up a bit, we could > take gameplaying as an example, where specifications would involve > writing the rules of games like chess and Go. Looking further ahead, a > highly desirable application area would be verifying, debugging and > configuring existing software, the interface to which would entail > writing specifications of existing languages and platforms. Fancy > writing a C compiler or a Java byte code interpreter in raw lambda > calculus?
If that allows AI to understand the code, without directly helping it. In this case teaching it to understand these other languages might be a better first step. But, speaking of application to debugging software, I long ago came to conclusion that you'd need to include unreasonable amount of background information which you won't even be able to guess relevant to make AI do what you need with things that are not completely defined. I feel like I'm advising washing hands before shooting yourself in the head, to avoid infecting the wound. Generally sensible advice, but doesn't really apply to this idea, which is just a wrong thing to attempt in the first place. -- Vladimir Nesov [EMAIL PROTECTED] http://causalityrelay.wordpress.com/ ------------------------------------------- agi Archives: https://www.listbox.com/member/archive/303/=now RSS Feed: https://www.listbox.com/member/archive/rss/303/ Modify Your Subscription: https://www.listbox.com/member/?member_id=8660244&id_secret=117534816-b15a34 Powered by Listbox: http://www.listbox.com
