search for: addtrack

Displaying 4 results from an estimated 4 matches for "addtrack".

Did you mean: adtrack
2009 Apr 02
0
FLAC: joining source files
...is much heavier to implement) -- and may pose issues with meta info like seekpoints, cuepoints ... ========= snip snip ========== #!/local/bin/perl use strict; our( @spt, at tr ); sub usage { print "USAGES:\n\n$0 cddb_id [...]\n\n$0 cddb_id start_track end_track\n"; exit 1; } sub addtracks { my( @y, $k,$nfo,$nsp,$p,$z ); usage() if $_[0]!~/^[0-9a-f]{8}$/; # build list of PCM files if ($#_>0) { for ($k=$_[1];$k<=$_[2];$k++) { if ($k>9) { $p='' } else { $p='0' } push @y,$_[0].'_'.$p.$k.'.wav'; } } else { opendir D,'.';...
2025 Jan 18
4
Parser For Line Number Tracing
...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'?
2025 Jan 18
1
Parser For Line Number Tracing
...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...
2025 Jan 19
1
Parser For Line Number Tracing
...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...