Help with structs and lists

[RPC]

I looked at this but Trans had issues with starting, so I decided to do something on my own.
The idea is this:
I will create a Star Network list like this:
(NodeID1 {Inbound: "List" Outbound:"list"} NodeID2 {Inbound: "List" Outbound:"list"} etc)
Through code, I'm planning to do it like this:
http://paste.neurohack.com/view/YYU6R/
However, it's returning this:
http://paste.neurohack.com/view/YMmnY/
The final product will involve typCreating system topology nodes and creating them with the right amount of gates. (which will be later)
Starweaver also suggested to make the nodes and just link them using sysAddStargateTopology. Is that a better way to go? I really want to have a list of all connections so that I know how the topo looks like, but I'm starting to think it's unnecessary.

The issue I think I'm having is that setting the struct using setq isn't enough: I am not changing the list item in any way.
There's also the issue of SetItem not being able to create a key for a non-struct, which is a huge roadblock to this enterprise.

[RPC]

Also, the lambda:
http://paste.neurohack.com/view/Y855a/

[RPC]

Ok, I think I found the issue (again ). Apparently each item in the list, whether it be a struct or item, has no relation to each other. This means that when I enum this:

Code: Select all

(Ares_Prime "St._Katharine's_Star" { Dummy:Key Inbound:("St._Katharine's_Star") } { Dummy:Key Outbound:(Ares_Prime) } E { Dummy:Key Inbound:(E) } { Dummy:Key Outbound:("St._Katharine's_Star") } C { Dummy:Key Inbound:(C) } { Dummy:Key Outbound:("St._Katharine's_Star") })

each element is not processed as:
E { Dummy:Key Inbound:(E) } { Dummy:Key Outbound:("St._Katharine's_Star") }
but rather
E
{ Dummy:Key Inbound:(E) }
{ Dummy:Key Outbound:("St._Katharine's_Star") }

Does that mean I should switch to making the Network list full of structs, like this:
Networklist -> ({NodeID: "ID" Inbound: "List" Outbound:"list"} {NodeID2: "ID" Inbound: "List" Outbound:"list"}) etc?

[alterecco]

Code: Select all

(setq systemList {NodeIDWhatever: {Inbound: "PreviousNode" Outbound: "NextNode"} AnotherNode: {Inbound: "PreviousNode2" Outbound: "NextNode2"}})

At least that is how i would do it. The biggest issue is not being able to get the name of the node (since it is a key, not a value). One option there is to add a name: "NodeIDWhatever" to the struct for each node.

[RPC]

Yeah, I noticed that. I think I'll just add a struct for the node name.