4 ms·
Is "ported" the right term here? It know the repo's README says "CGo-free port", but this is the C version of TCL transpiled from C to Go (see the ~13MB .go fil
by benhoyt 4y ago
Is "ported" the right term here? It know the repo's README says "CGo-free port", but this is the C version of TCL transpiled from C to Go (see the ~13MB .go files per platform in the "lib" directory). Which is a very cool idea, and the author has done the same thing with SQLite, to avoid CGo (https://gitlab.com/cznic/sqlite https://gitlab.com/cznic/sqlite).
Here's a link to his C to Go translator: https://gitlab.com/cznic/ccgo https://gitlab.com/cznic/ccgo
- svnpenn 4y agowhoa you weren't joking, what the hell: https://gitlab.com/cznic/tcl/-/blob/master/lib/tcl_windows_amd64.go https://gitlab.com/cznic/tcl/-/blob/master/lib/tcl_windows_a...
- Grimburger 4y agoNothing says "easily maintainable" like a 298,000 line go file. Gitlab is struggling to render it for me.
- CodeSgt 4y agoCan't lose context if you never leave the file.
- omegalulw 4y agoCan't have context if the file never loads.
- MobiusHorizons 4y agoSounds like you need a better editor :) But seriously, I would expect most editors to handle large files relatively gracefully, even if they aren’t as fast as vim for example. Browser based code viewers on the other hand, I grant you, aren’t generally up to the task.
- benhoyt 4y agoThis is of course generated code (output from the C to Go converter), so to "easily maintain" it, you'd edit the Tcl C source files and re-generate these. The generated Go code is committed to the repo so the person using the library doesn't need the C-to-Go converter tools.
- nurettin 4y agoThat is just a compilation artifact, though. He only commits it for online importing.
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]