search

solent-eng / solent

Free software sequencer architecture
GNU Lesser General Public License v3.0
7 stars 4 forks source link

improve nearcast_i so we can deliberately name a nearcast #104

Closed cratuki closed 6 years ago

cratuki commented 6 years ago

A solent application can have multiple nearcasts. It can be difficult to follow the logging for this, and for a single reason: the orbs named are generated, and these generated names are unhelpful. Through this issue, we will make it easy for developers to give more useful names to their orbs.

(By orb 'name', I mean he value held in orb.spin_h)

Currently, nearcast_i shows this interface:

    i message h
    i field h

We should change it to this

    i schema h
    i message h
    i field h

Schema is an optional field. If the user sets it, then the orb will take its spin_h value to that.

This is a simple change, and it will make a significant improvement to debugging.

cratuki commented 6 years ago

Hmm. We do not want to change spin_h. That is a unique key that is owned by the engine, and used in the engine.

Rather, we want a new concept of orb_h. By default this is copied from spin_h. But the user can override. The snoops should use this value rather than spin_h.