3 ms·
STL has an ascii variant if you like. But the real issue is placing derived files under source control. There's no good answer here. If the STL is the output
by ajross 14y ago
STL has an ascii variant if you like. But the real issue is placing derived files under source control. There's no good answer here. If the STL is the output of, say, a script engine that generates parametrized parts, then of course it shouldn't be in git. If it's the output of a manual process in an interactive tool (e.g. a CAD program) then the distinction is fuzzier. It's not really the "editable source", but then neither can it be automatically derived by a build system.
- derefr 14y ago> If it's the output of a manual process in an interactive tool (e.g. a CAD program) then the distinction is fuzzier. It's not really the "editable source", but then neither can it be automatically derived by a build system. It sounds like what you'd really want, in that case, would be an ASCII-encoded log-structured manipulation-history format--sort of similar to a Redis Append-Only File.