Peter Tillema

Update: all the exported variables should have `1A 0A 0A`, except in the following cases: - if a string/appvar/(protected) program contains any CSE or CE tokens (like the colors), it...

Which means that (complex) numbers, (complex) lists, matrices, window, table and zoom variables should still have 00, while the others at least 0A, and eventually a higher number (will explore...

I've tested several "new" tokens so far, but it seems every CE-only token is `13`, CSE/CE is still `0F` and normally it's `0A`. Can't guarentee this applies to everything of...

> > > well it probably doesn't matter if it can't send them to older calcs since they wouldn't actually be compatible anyway (but if it does transfer some vartypes...

Any updates on this?

Well, it is actually very easy. Loop through the program, and get all tokens. Then check the version of each token, which is like checking if the bytes are between...

> > > The third byte is actually what's called the "owner calculator ID", and it can have the following values (that I have seen so far): https://github.com/debrouxl/tilibs/blob/master/libticalcs/trunk/src/ticalcs.h#L166-L191 here you...

Update: what I wanted already exists, namely `parse_docstrings` in `miss_hit_core/m_parse_utils.py`. Now I only need to know if single comments can be added somehow...

This is indeed a tough question, so let me dump here my thoughts about this. > > ``` > x = 1; > % potato > x = 2; >...