LLL
Dr. J. Van Sckalkwyk (external)
SCHALKW@odie.ee.wits.ac.za
Thu, 22 Dec 1994 20:02:15 SAT
rideau@clipper.ens.fr Francois-Rene Rideau
Dear Fare
I'm just doing an informal little survey to glean a few
facts from everyone. Care to contribute your feelings?
LOW LEVEL DESIGN QUESTIONNAIRE (BRIEF)!
=======================================
This is not a call for vote!
IMAO (in my arrogant opinion), there seems to
be a potential design problem. Mike seems happy
to use C for the initial coding for the
"common language" that will run on all machines
where we implement "Joy". I am _not_ happy
about this decision mainly because:
(1) I am not sure that C is up to it!;
(2) I believe that this will bias our
design and lead us to ignore viable options;
(3) I think it violates KISS.
The justification for a "common language" is
outlined in the postscript to THIS message.
I may be completely wrong. I would like to
gauge the general feeling (I don't want to
waste bandwidth if everyone is clearly for /
against one option, or indeed, totally NAAFI).
Instructions:
Please put an X in the appropriate box(es)
ie [] ====> [X]
and mail to me (schalkw@odie.ee.wits.ac.za)
I will post outcome in 8 days (promise)!
START
|
|
1. Do you think the problem
exists and is relevant?
/ \
/ \
YES [] NO []
| |
| |
| Thanks for your time---> EXIT
|
2. Let us call our common "symbolic assembly
language" SYMBAL, as J seems to be out of
bounds. What should be used to create the
core code for our system on each machine,
SYMBAL or C?
Choose only one:
|
********************************************************
Strongly Favour SYMBAL ? / Needs Favour C Strongly
support | more | support
SYMBAL | discussion | C
| | | | |
[] [] [] [] []
| | | | |
**************************************************
|
|
|
3. Do you have reasonable practical experience in programming
any of the following at assembly level?
Processor Check if "YES"
--------- -------------
80x86 []
P5 []
68000 series []
Other: (please state) []
1.
2.
3.
4.
*******************************************
|
|
Did you answer [X] (yes) to any of the above?
/ \
/ \
NO [] YES []
| |
| |
| |
| would you be interested in co-operating on
| developing a common "symbolic assembly language"
| for several processors, specifically tailored
| so that we can use it to develop higher extensions
| (eg. Mike's cells)?
| / \
| / \
| Yes [] No []
| | |
******************************************
|
|
|
4. Are you proficient at C programming?
/ \
/ \
Yes [] No []
| |
| |
| Thanks for your time---> EXIT
|
5. If C is chosen for core coding
would you be interested in
participating in this?
/ \
/ \
Yes [] No []
**************************
|
|
Thanks (the end)!
JVS <
P.S. Below is an excerpt from a previous post of mine,
justifying a common language.
>START SNIP<
If cell A migrates from machine X to
dissimilar machine Y, it presents similar external
characteristics in terms of its interaction with other
cells [..]
Assumption: Our goal is achievable. Otherwise, we're wasting
our time.
Assume: goal has been achieved. ie we have:
LOWEST (HARDWARE) LEVEL -------|----------> HIGHEST (CELLULAR) LEVEL
|||||| | ||||||
DISSIMILAR MACHINES -----------|----------> SIMILAR CELLS
|
transition point.
Below the transition point, function will be dissimilar.
Above, similar.
Now, I see our problem as "trying to define the
common language immediately above the transition point".
>END SNIP<
JVS<