Re: verilog-ams instance loading

On Tuesday 27 January 2009, John Griessen wrote:
> What would it be like to change the verilog-ams input
> parsing?  What kind of version control methods do you use for
> dealing with volunteer code patches?  Will you point  me to
> the place to look in the code?

The verilog code is in "lang_verilog*".

The best way to work on it is to treat it as a plugin.  

Grab that set of files, compile with 
"g++ -shared -fPIC -o verilog.so lang_verilog*cc"

Then "load ./verilog.so" and to substitute the new version.

> Is changing verilog-ams input parsing in the category of
> "usability coding" that you have written about dropping in
> favor of "forward progress coding"?  I paraphrased -- not
> quoting you and may have read wrong.

What I said is that I have imposed a temporary "feature freeze" 
because there are a lot of new features since the last stable 
release that are not adequately tested and documented.  My 
focus for now is to test, fix, and document, then make a stable 
release.