when thinking about hardware layer of the Stitie Processor cubes, ideas come to my mind,

how to handle limited amount of memory in a single Stitie Machine?

perhaps State can have a links (pointers or references) to other memory parts, perhaps in different Spaces.

these referenced memory parts might together form an address space, a flat,
1-dimensional, State's a part.

this 1-dimensional space can be arranged many ways, for example as classical up-down memory address list that contains instructions & data.

other possible forms are theoretically possible, but i fail to see reasons for these, perhaps future will correct me in that.

there might be method that reserves a given selection of stitie machines & produces State object that hides these links & references from user's awareness, providing simpler model as for example Hash Map to protect his or her sanity, to increase productivity as well.

Pseudocode might look as that:

  StitieSpace space1 = ...;
  StitieSpace space2 = ...;

  Coordinates[] coordsList = { ... };
  State smA = space2.getFlatStateFromMachinesAtCoords(coordsList);

  StitieMachineImpl machineA = space1.getStitieMachineAtCoords(...);

A part of Stitie Computer, consisting of many Stitie Processor cubes (shown on image below as colored spheres) might look as that:

Green Machines belong to Stitie Space #1,
Grey Machines are unassigned,
Blue Machines belong to Stitie Space #2.

(connections & infrastructure were hidden on this image for picture's clarity).

Stitie Space's Object that creates State for example would be a part of infrastructure electronics, placed in-between individual machines.

a warning: 'Combining State' article is not very related to what i am doing here.

No comments:

Post a Comment