From: Andy G. <and...@gm...> - 2019-04-08 06:28:47
|
I'd like to put my pipeline package into Tcllib, but it depends on my argparse package which is not in Tcllib. It may seem like the obvious solution is to also put argparse into Tcllib, but I'm not sure how well that will work with my long-term goals for argparse. Right now argparse is written in pure Tcl 8.6, but once I knock out the rest of my interface-relevant ideas, I want to reimplement it in C to be a loadable extension with a stubs-enabled C API. That makes me think it should be its own TEA-compliant project rather than a Tcllib module, but then if I don't put argparse into Tcllib, I shouldn't put pipeline or other packages that depend on argparse into Tcllib either. Guidance? Thoughts? https://wiki.tcl-lang.org/page/pipeline#853e5dc13add203ce4b75e513189e8f07dc4af458b61e91ce34c3afea8c1e210 https://wiki.tcl-lang.org/page/argparse -- Andy Goth | <andrew.m.goth/at/gmail/dot/com> |