[PD-dev] broken msgs cause Tcl traces, how to debug it?

Miller Puckette msp at ucsd.edu
Mon Jan 23 06:54:45 CET 2012

As it stands right now, there are new-lines in the middle of certain tcl
commands sent from Pd, so if newline were it, I'd have to go chase down all 
the pretty-printing newlines in the Pd code and delete them.  That might
actually might work; I'd only be worried taht some extern was throwing up tcl
code with intra-tcl-statement newlines that would occasionally throw false
positives at the tcl completeness checker, if indeed all it did was check
that the tcl buffer ended in a newline.


On Mon, Jan 23, 2012 at 12:45:09AM -0500, Mathieu Bouchard wrote:
> Le 2012-01-22 à 21:16:00, Miller Puckette a écrit :
> >There's not much way around this.  One possibility (if indeed this
> >is a serious efficiency issue) would be for Pd to append a "done"
> >message to each batch up tcl to up-send.
> That's called a newline... not preceded by a backslash. The thing
> with fconfigure -buffering line is that it doesn't care about
> backslashes, whereas eval does, and if you use both together, you
> need to account for that difference.
>  ______________________________________________________________________
> | Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC

> _______________________________________________
> Pd-dev mailing list
> Pd-dev at iem.at
> http://lists.puredata.info/listinfo/pd-dev

More information about the Pd-dev mailing list