search for: addtracker

Hello, Here's a script i use to join multiple PCM source files and feed them to FLAC. In the future i plan to add tag support from static CDDB (files). It would be nice if this feature could be incorporated to the native encoder. Another idea is to have flac/metaflac support joining FLAC files themselves (but this is much heavier to implement) -- and may pose issues with meta info like

...ysterious in themselves, too, making it even harder.) the way I do it is mostly with inserting `message()` statements. what I would really like to have is a parser that inserted 'curline <<- ##' into the R code, where '##' is the filename and line number. something like 'addtracker one.R two.R' and thereafter I can run two.R and, when the program dies, use `print curline` to find out where my error has roughly occurred. has someone already written such an 'instrumenter'?

...too, making it even harder.) the way I do it is mostly with inserting > `message()` statements. > > what I would really like to have is a parser that inserted 'curline > <<- ##' into the R code, where '##' is the filename and line number. > something like 'addtracker one.R two.R' and thereafter I can run two.R > and, when the program dies, use `print curline` to find out where my > error has roughly occurred. > > has someone already written such an 'instrumenter'? > > ______________________________________________ > R-help at r-...

...too, making it even harder.) the way I do it is mostly with inserting > `message()` statements. > > what I would really like to have is a parser that inserted 'curline > <<- ##' into the R code, where '##' is the filename and line number. > something like 'addtracker one.R two.R' and thereafter I can run two.R > and, when the program dies, use `print curline` to find out where my > error has roughly occurred. > > has someone already written such an 'instrumenter'? The basic R parser already does that. For example, try putting these li...