On Fri, Aug 29, 2014 at 9:11 AM, Joe Mistachkin <sql...@mistachkin.com>
wrote:
> It would be _much_ easier now. My view is this: I view TH1 purely as an
>
avenue to access Fossil-specific commands and expose them to Tcl, period.
> If I wanted to do serious custom script development with Fossil, almost
> all of the "TH1" scripts would look something like:
> tclEval {
>
# invoke a TH1 command...
> th1Eval [list trace "starting Tcl script"]
>
If that provides me with at least line/column info (filename when including
multiple files), then i'm happy. Plus points for stack traces ;). (IIRC
JimTCL can do those.)
i looked into adding line/col info to th1 early on, but just didn't see how
to get it into those structures.
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
