🚀 go-pugleaf

In article <446@afit-ab.arpa> cbaron@icc.UUCP (Christopher T. Baron) writes:
>Anyway, while I was returning to Dayton from Ami-Expo an idea came to
>me that the Amiga, being  a multi-tasking system,  could benifit from
>system  level  support  for  several of  the  traditional AI type  of
>functions.  By this I mean an inference engine, a  state space search
>routine such as A*, and  say a built   in natural language  interface
>(text).

-- Sure would be nice!

>The mind reels under  the number of  ways system and  user perfomance
>could be improved.

-- The mind also reels at the processor bandwidth required to actually
-- improve performance by using a rule based engine to do all this.
-- :-) It might help on an 68030 machine, which really should have
-- several spindles to feed it, but by now I assume that everybody
-- realizes that Amigas only use hard disks as slow non-volitile
-- memories.

>My initial thoughts on implementation is that the services would be 
>implemented as a shared library, with functions for:
>  
>   A backward and forward chaining inferencing engine
>   A rule base compiler
>   One or more state space searching algorithms
>   system modification such as task priority modification
>   the ability to start/suspend/kill tasks
>   an i/o section for interface with the user i.e. a uniform query facility
>   special alerts for output
>   natural language parsing into a language independent form with
>   system and/or user dictionarys

-- The first three items would be an excellent product. The
-- compiler should probably be a tool with a CLI interface, but in any case
-- should be packaged separately.  There would be many applications
-- which woould have a static rule base, and could not afford the
-- space for a large library.

-- These tools would  be a  hell  of a   product. Add Common  Lisp and
-- Scheme, and  Amigas will replace Sun Workstations  on a lot   of AI
-- projects.  (Just   like Suns have  replaced  Lisp Machines...) Next
-- project after IPC anyone?

					Robert I. Eachus

with STANDARD_DISCLAIMER;
use  STANDARD_DISCLAIMER;
function MESSAGE (TEXT: in CLEVER_IDEAS) return BETTER_IDEAS is...