You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Taking inspiration from the definition of the object in uLisp you could use a C union for tcl_var to be able to represent linked lists as more tcl_vars:
struct tcl_var {
tcl_value_t *name;
+ union {
tcl_value_t *value;
+ struct tcl_var *values; // Pointer to nested list or hashmap+ }+ char type; // Flag to determine which pointer in the union to take
struct tcl_var *next;
};
The name would hold a string of the index (possibly in hexadecimal, to speed array lookup).
Now that a var can point to another var, this could also lead to hashmaps (name being the key string etc) and nested data structures.
Does this sound like a possibility?
The text was updated successfully, but these errors were encountered:
Taking inspiration from the definition of the object in uLisp you could use a C union for
tcl_var
to be able to represent linked lists as moretcl_var
s:The name would hold a string of the index (possibly in hexadecimal, to speed array lookup).
Now that a var can point to another var, this could also lead to hashmaps (
name
being the key string etc) and nested data structures.Does this sound like a possibility?
The text was updated successfully, but these errors were encountered: