Eric Baum wrote: > My bad language. I didn't mean code written in the language > Occam (which I'd forgotten about, don't know anything about it).
Ha, I was wondering, but unfortunately I didn't have your book to hand to check. I'm almost disappointed; Occam /is/ an interesting language that certainly could support some novel (narrow) AI work. > I meant, code in some constrained language (for example, constrained > by being very concise) that solves so many different problems that > such constrained code wouldn't exist unless it was fundamentally > exploiting structure underlying the problem-- code exemplifying my > generalized Occam's Razor hypothesis. Would you include typical VM bytecode (e.g. JVM/.NET/Parrot/Emacs Lisp/etc) in that class, or does it need to be more specialised? How about a Huffman-compressed version of the code causality graph, from the basic operators (and library functions if applicable) up? Michael Wilson, Director of Research and Development, Bitphase AI Ltd Web demos page: http://www.bitphase.com/apex ----- This list is sponsored by AGIRI: http://www.agiri.org/email To unsubscribe or change your options, please go to: http://v2.listbox.com/member/?list_id=303
