Kim Gräsman

@aldas Thanks -- > assembly is up to you to implement. Ah, yeah, then I hadn't missed anything. I got the impression from above that there was reassembly support built...

It might be a while until I get to this, but this: `pyparsing.ParseException: Expected "DEFINITIONS" (at char 195), (line:8, col:13)` is a good place to start. You can run your...

So is line 195, col 37 at the end of the file? Can you upload the ASN.1 as text so I can see it?

Yeah, that explains it. asn1ate doesn't support CLASSes, and I don't really know where to start on that, so I think it's safe to assume that it won't do so...

Sorry this took so long (my time for asn1ate has been very limited), but I got around to experimenting with this today. It turns out that `true` is not a...

It could be that dependencies are not wired between modules -- I have quite elaborate logic in place to detect dependencies and generate assignments in dependency order, not sure if...

Yes, at the semantic level. Oh, now I see you say PDU-definitions disappears from the parse tree... I think that might be because `--parse` only dumps the parse tree of...

Thanks for the contained repro. I seem to recall [this PR](https://github.com/kimgr/asn1ate/pull/21) added support for emitting modules to individual files, maybe that would help here? Looks like there's a `--split` argument...

> Oh, now I see you say PDU-definitions disappears from the parse tree... I think that might be because > `--parse` only dumps the parse tree of the first module,...

No, I don't think I ever got around to solving this entirely. It was harder than I thought, and I ran out of time.