Lars Kellogg-Stedman

I thought about that, but there are situations where I would like to use the same table in multiple places. I guess I could make it some sort of top-level...

You can see an implementation of that idea [here](https://github.com/larsks/tm-v71-kaitai-example/commit/5e73355de27aa479883fcaca275b84732eb4c0f9#diff-0b768f56fb0d99237b181ed5e69b7239R49) and [here](https://github.com/larsks/tm-v71-kaitai-example/commit/5e73355de27aa479883fcaca275b84732eb4c0f9#diff-0b768f56fb0d99237b181ed5e69b7239R158).

They're not for "presentation", but neither are they required for further parsing. They are the real values that the numeric constants in the binary data represent: that is, they are...

@KOLANICH I'm not really sure how that would look. Can you share an example? I mean, I've used `switch-on` for type switching, but I'm not sure how that would be...

@KOLANICH Thanks! I had no idea you could do that. The user guide only shows `switch-on` in the context of selecting a `type`. I'll try that out.

Oh wait, I think you're suggesting a possible **future** syntax to implement this! If that's the case, :+1: to that idea, because it would work really well.

Note that the workaround I'm using (lookup tables as value instances) appears to be buggy, see #632.

Or I guess more correctly: ``` class Namespace apiVersion: str = Field("v1", cont=True) kind: str = Field("Namespace", const=True) metadata: ObjectMeta ```

The problem with the nova analogy, of course, is that all of those tools - novaclient, opentackclient, horizon, etc. -- expect the Nova API server to be running, and communicate...

@buserror , I was going to open a similar issue, but then I stumbled upon this one. I am writing some code targeting an attiny85, and I am trying to...