|
<![CDATA[
Hi John,
Thank you for sending the assembler picture
it clearified the concepts of webaxons and
webstores to me.
As I understand it a webaxon is for storing/sending data
to another webneuron. And a web store is for storing 'static
data' (for example the time data for calculating
firing frequencies if we want to model this).
I will go more into webaxons and webstores in my other mail
(DATA).
The use of the LUT is not complete clear. I understand
CALLER, TARGET, HOST are looked up in the LUT which returns
the address. Is this correct?
I think your views on multitasking are a bit simplistic:
use a stack and you've got multitasking. (This is much like
MS Windows multitasking, which is not really multitasking).
As I understand the XLUT and LUT is that they are an array
of pointers. I whould NEVER ALLOW ANOTHER COMPUTER TO
DIRECTLY MAKE CALLS TO MY RAM.
On the use of language
I think you're assembler model can easily be implemented using
other languages as well. For example using C++ you can make a CLASS
webneuron:
(webneuron.h)
/* This is just a simple framework
* for a WebNeuron Class (The classes
* List and Axon ar not given here)
* the syntax might not be completely correct.
*/
class WebNeuron {
public:
Axon *fire(Axon *in); //fire function takes a pointer to (input) axon
//as argument returns pointer to (output) axon
private:
Webstore *wb; // pointer to webstore
List <Axon *> *outputaxons; // list of output axons
List <Axon *> *inputneurons; // " " input "
};
/* To write a new neuron we just have to implement the fire function
* for example to make a Webneuron: A
*/
a.ccp
class A: public WebNeuron {
public:
Axon *fire (Axon *in) {
// the code //
}
}
I don't care which languages we use. But I prefer C or C++. (Linux
is written in C).
They can also draw them using my idea
webneuron A:
input = (axons or webneurons)
| | | | | = links to the map of
the script
MAP of Script (A)
\ / \ / \ /
> = > = testing output of script
/ \ / \ / \
output = (axons or webneurons)
This could be a template and wen you zoom out you get for example
get
\ / \ / \ /
webneuronA webneuronB webneuronC
\ \ / (B)
webneuronD - webneuronE
/ \
And you could zoom out:
webletA webletB
\ /
< (C)
/ \
webletC webletD
As you can see the distinction between maps A B en C is quite
arbitrary (or the names you give them depend on your point of view).
Futher more you can now add/ compare etc output of webneurons weblets
etc. in a simple (and intuative way).
You may have noticed I didn't much use the axons I will explain this in
the other message.
As I've mentioned before the largest part of the problem (wether we
use my model or yours) is the interface. We could begin by writing
a program for drawing maps (after its clear how we do the hubs)
which translates those maps to C (and if its possible the other way
around so C source can be converted to maps).
Regards,
Frank
____________________________________________________________
Drs. F.P. Schuurmans CYBER PUBLISHERS
frank@bio.vu.nl Amsterdam, The Netherlands
]]>
|
Frank's Emails
Re: ASM - re:assembler