gnucap-geda, sym file hndling (was Re: sym to verilog-ams)

Felix:
...
> It's much the same as schematics. geda has top level objects, and
> verilog doesn't, so you put everything into a module definition. The
> goal is to reproduce the sym file back from its verilog representation
> (round-trip).

The sym files usually stays unchanged. Why not just include the file 
name of the sym file and its checksum/git commit/svn commit/etc.

If the checksum is changed we can do a lossy repair of the original file
which will work as originally inteded or check it out from a repository.

I have http://aspodata.se/git/openhw/git_show
$ ~/git/openhw/bin/git_show _discrete/res_h.sym
2021-07-04 15:32:46 42c241a2 _discrete/res_h.sym

$ svn info --show-item last-changed-revision Makefile.in 
33700

> In the schematic tests, I use the "list" command, and "list main" prints
> the main module definition (in verilog mode) and the contents of the
> schematic (in geda language mode) respectively.

What is this "list" command you talk about ?

> gnucap-geda has an ad-hoc symbol implementation in src/symbol.h dating
> back to 2012. It sort of serves the purpose, but it must be implemented
> correctly.
> 
> - GEDA_SYMBOL must become a plugin.
>    either use subckt from d_subckt.cc, or something similar derived from
> 	BASE_SUBCKT
> - The parser in GEDA_SYMBOL::GEDA_SYMBOL must be singled out.
> - GEDA_PIN must be a plugin as well.
> - GEDA_SYMBOL_MAP, where libgeda is (ab)used, must be dropped.
>    (this is strictly off-topic.)

I'm not up to speed with this.

Regards,
/Karl Hammar