======================================================================
From: TIM RUE                   Conference: 240 , I-Programming

Subj: V.I.C. -- 1 of 10         Date: 02-08-95  Time: 22:48
----------------------------------------------------------------------
 > * In a message on 02/05/95, ----N---- said to TIM RUE:
 > N> TR>     PLEASE NOTE!!!
 >
 > N> Tim,
 > N>      A couple of suggestions.
 >
 > Also, shouldn't there be a rule somewhere about being meaningful?  This
 > paper of his made no sense to me whatsoever.  I can build the world's
 > best artificial intelligence engine, too, but it's just in my
 > imagination that it actually works.  :)
 >
 >

  -----, focus on what you do understand. Being that this conference
  is "Programming", I believe you would understand the description
  of the parts and how they relate to what does exist. The V.I.C.
  can be built, I'd have already done this but my programming skill
  and knowledge vs: available time, simply hasn't allowed me to do
  so. And although I mentioned A.I., I would not say the VIC is an
  A.I. engine, though it can be used as a building block for such.
  It can also be used as a building block dealing with robotic
  movement or a building block for automated programming, etc... Or
  any combination of building blocks, integration of robotics, A.I.
  and automated programming for example.

  But from a programming conference perspective, the VIC can be
  built. It's the first step. If there is something not clear to
  you about the defined functionallity, ask.

  AWK originally was not intended to be used to the extent it now
  is. That is, full length (1000's of lines of script/code for a
  single AWK program). And in consideration of what has come about
  with AWK, the VIC is designed/defined to allow virtual
  configurability. How it may be used is up to users, but unlike
  AWK the constraints are left up to the user to define. The VIC
  configuration objective is to not have any inherent constraints
  which would constrain usability.

  I have no doubt I could show you examples of use, knowing others
  will come up with uses I haven't imagined. But again the problem
  is in seeing it work and this cannot be done without creating the
  VIC. And the VIC can be built and as defined!

  Within the world of programming where one can see in only one
  direction, even though through experience with different
  languages ones sight can become wider, one still has limited
  sight. But from the outside looking in one can see the whole,
  and with effort one can better determine the primary constants.
  Fortran is a good language for number crunching but the ICON
  programming language is better for non-numeric programming. The
  difference is in the built in or inherent constraints of each
  langauge. Each having it's up-side and it's down-side. Although
  it's possible to combine compiled code from different languages
  into one program, there are still constraints which require the
  programmer to fully understand the languages being used. But to
  have the ability to define constraints sets and change between
  sets in the sequencing of a process one is given the ability to
  control the constraints rather than the constraints controlling
  programming. The VIC allows for one to create and change the
  rules.

  It is not outside the VIC ability for constraints to be defined
  that allow it to compile C code or any other code. But its ability
  goes beyond programming and into application. The three levels of
  development, the VIC, the Alternating interface (internal as in
  VIC use as well as external or user interface), and the Knowledge
  Calculator that allows the user to work on a higher level with
  greater ease - built upon the AI (or defined constraint sets)
  which in turn is built upon (processed by) the VIC.

  -----, when I began learning about programming I found examples
  that seemed to be pointless, made no sense, but as I learned more
  and looking back I understood. For any experienced programmer I'm
  sure the creation of the VIC would be fairly easy. For myself,
  I know I could create it, perhaps I will, but I've got to find
  the time to learn and do it in the multi-tasking environment of
  the Amiga (because it's the system I have and I want to take
  advantage of multi-tasking). I learned C on/in the environment of
  single tasking MSDOS. Big difference in environment.

  The C programming Language has "no functions". It is a definition
  of a langauge of which C compiler makers adhear to. There is a
  library of functions which have become standard and may be built-
  in to the compiler. But the function are not the "C programming
  language." Functions are built upon the C language definition.

  The C programming language is a set of constraints. A set that is
  likley never fully/completely used in any one program. A program
  contains, and makes use of, a subset of the full set.

  The VIC allows one to define the language(s) or constraint sets and
  to change between constraint sets. And sense the user/programmer
  is allowed to define the constraints and change them during
  processing, the user/programmer is not constrained by unchangeable
  constraints.  And it is this that may be difficult for you and
  others to understand. I'm not setting any rules or constraints, I
  only identify and define the mechanics that will allow you to define
  the rules or constraint set(s). And I'm doing it on a command line
  level, as a primary interface level, so to not only allow versatility
  but anyone to make use of it (from kids to professional programmers
  and researchers of non-traditional-programming fields.)

  "it's just in my imagination that it actually works. :)" Your mind/
  brain is a physical device that processes abstract thoughts/
  imagination. A computer is a physical device that processes abstract
  concepts created by mans thoughts/imagination. The difference is clear.
  Both originate from man and deal with man created constraints. A
  computer is detached from man and the VIC has the inherent constraints
  of hardware but need not be constrained more than this. What good is
  your imagination to the rest of us, if you do not communicate what your
  imagination creates. To communicate successfully requires structure and
  definition(s). Structure and definition(s) can be (and are) represented
  with the basic computer elements, the bits. Movement/flow and change
  are also relative to communication.

  I hope I've shed some light here for you -----. The bottom line remains
  (at this time) to be creating the VIC. And it is defined and buildable.
---
  RNET 2.006: ILink: Faster-Than-Light  Atlanta GA USA  404-292-8761







Email: timrue@mindspring.com

Copyright © 1988, 1994, 1996 Timothy V. Rue