I've been using halscope frequently for a number of distinct purposes but don't
like setting it up or wrangling the config file (.scope.cfg) each time so I
made a simple change to halscope that lets a user specify an input file to read
and/or an output file to write for configuration items.
Modified behavior:
$ halscope -h
Usage:
halscope [-h] [-i infile] [-o outfile] [num_samples]
The current behavior is not affected.
John Kasunich suggested I post about it here to see if there's
any interest in adding a patch to CVS.
The one modified file (scope.c) is posted at:
http://pastebin.ca/1021409
dgarrett
--
Dewey Garrett (925)447-9364
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
