Hi Mike,
thank's for the new versions. Now it keeps the include statement for my library. The simulation works fine. I did another test and the following question came up: What happens to the report to stdout? I discoverd it because the circuit file had an error. When I run ngspice in batch mode (ngspice xxx.sim -b) I get a detailed reprot on the screen and I can find out what the problem is. Can I find this log somewhere on the disk? Peter Am Mittwoch, 10. November 2004 04:25 schrieb MSWaters: > Hi Peter, > > > as far as I understand your program, you parse the Spice input file for > > the ".include" statement. When you find one, you copy the included file > > to the spice input file and create a simulation file. > > GSpiceUI expects a net list as input and just extracts the basic net list > stuff ignoring everything else. A simulation is created by adding the > appropriate SPICE commands to the parsed net list stuff. > > > What do you think about a switch, wheter to include the file or leave the > > include statement. For teaching purposes or for small simulation it's > > very usefull to have everything in one file. For simulation with huge > > libraries, it might be confusing to get a large file with all the library > > elements. > > I have no problems with include directives it was just something that I > didn't think of. I've modified the code so that includes don't get filtered > out and IN-exaustively tested it. I've attached a tar.gz of the new sources > for you to try. Let me know how you go. > > By the way for anyone who is interested there is a development snapshot of > GnuCAP at http://gnucap.org/devel/ dated 2004-10-09. > > Regards > Mike Waters
