Andreas Kupries

> all of them seem to be written by, and for, (a) computer scientist(s), with much implied and expected Definitely by a computer scientist (i.e. me). ... And being well-versed...

> When is it in 2022? No idea yet. > that a critcl::cproc gets a Tcl_Interp* on input Look at the cdc package, cdc.tcl, line 48. It is a special...

I have started on the reorg and hopefully the new howto's will reach error signaling before you are getting back to working with critcl. :wink: That said, would you be...

Ok. In that case I believe I will simply push to a branch/PR you can then checkout. The readable docs will be under `embedded/www` ... I will mention again when...

>Was that a challenge? ;-) Remember my qualifier of `hopefully` in the comment. That said, #119 is the PR in which I work on the docs. Enough has been rewritten...

I prefer them here, in the ticket.

> what's the best way to pass large amounts of data (like a 50MB data block) to C and (my interest in particular) back to tcl? I suspect it depends...

> "not very useful" bytearray? [why? one could pass the size as a separate parameter?] Sure. Would look like a hack however. With a `bytes` type argument you invoke `foo...

> Upon reading, bytearray attracted my attention right away, and I was stopped by the comment of it being useless Ok. Greping through the docs it was only in the...

Ah, I forgot to respond to > I think the issue is the inconsistency, because C is a compiled language, and tcl is interpreted, I am expecting that if the...