http://gnucap.org/dokuwiki/ 2026-04-10T07:04:38-05:00 FeedCreator 1.7.2-ppt DokuWiki 2013-06-27T13:30:04-05:00 2013-06-27T13:30:04-05:00 2013-06-27T13:30:04-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:args?rev=1372357804&do=diff

parse, print args Background “Args” are the parameters of the device. Some languages read in args by order, some by name, some either way. When reading by order, the meaning is determined by the order in the list. A single value, such as resistance of a resistor, specified as just a number, is a simple case of reading by order. There is also a special case that allows you to identify one as the “value” and read the rest by name.

2023-11-02T22:17:25-05:00 2023-11-02T22:17:25-05:00 2023-11-02T22:17:25-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:attributes?rev=1698981445&do=diff

Attributes Background Sometimes it is desired to attach some meta-data, an “attribute” to some object. The name and the use of such attributes is determined externally by some other application. It has meaning there, but likely not to us. We just need to store it, to pass it on as we get it, unchanged.

2014-06-26T23:15:55-05:00 2014-06-26T23:15:55-05:00 2014-06-26T23:15:55-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:command?rev=1403842555&do=diff

parse, print command Background A command object executes a command, does not store anything. The reference to “dot” and “dotcard” is historical, because in Spice, commands were prefixed by a dot. This section may change as scripting is enhanced.

2013-09-06T19:52:51-05:00 2013-09-06T19:52:51-05:00 2013-09-06T19:52:51-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:comment?rev=1378515171&do=diff

parse, print comment Background A comment object stores a string, otherwise does nothing. For reference, here is the class definition from d_coment.h . /*--------------------------------------------------------------------------*/ class DEV_COMMENT : public CARD { private: std::string _s; explicit DEV_COMMENT(const DEV_COMMENT& p) :CARD(p) {set_constant(true);} public: explicit DEV_COMMENT() :CARD() {set_constant(true);} private: // override virtual char id_letter()const {retu…

2013-06-27T13:09:30-05:00 2013-06-27T13:09:30-05:00 2013-06-27T13:09:30-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:find_type_in_string?rev=1372356570&do=diff

find_type_in_string This function scans an input string and extracts the “type” from it. In some cases the type is explicitly stated and easy to find. In others finding the type can be tricky. In any case, scanning is reset to the beginning after the type is found.

2013-06-27T13:15:34-05:00 2013-06-27T13:15:34-05:00 2013-06-27T13:15:34-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:instance?rev=1372356934&do=diff

parse, print instance, paramset Background A netlist is primarily a list of instances. Synonyms for instance include component, device, element. Examples of instances include resistors, transistors. A paramset is a prototype for an instance. Internally, it is the same except that a paramset has no ports, but most languages have a different syntax for it. The word “paramset” is from Verilog syntax. In Spice, this would be a “model” statement.

2013-06-27T13:24:26-05:00 2013-06-27T13:24:26-05:00 2013-06-27T13:24:26-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:label?rev=1372357466&do=diff

parse, print label Background The label is a string by which this instance is known. In a paramset (Spice .model) the label is the name of the new type being defined. A “short_label” is the simple form of the label, without scope information.

2013-06-27T12:52:12-05:00 2013-06-27T12:52:12-05:00 2013-06-27T12:52:12-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:lang_base.h?rev=1372355532&do=diff

lang_base.h If your version of gnucap does not supply lang_base.h, use this one, copy it to the place where the gnucap headers are. #include "globals.h" #include "c_comand.h" #include "d_dot.h" #include "d_coment.h" #include "d_subckt.h" #include "e_model.h" #include "u_lang.h"

2013-06-27T13:16:55-05:00 2013-06-27T13:16:55-05:00 2013-06-27T13:16:55-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:module?rev=1372357015&do=diff

parse, print module Background A module is container of instances. To a compiler, a module can also contain code to be executed, but gnucap does not directly support that. A Spice “subckt” is a module. * type -- A module defines a new type. * label -- The label is the name of the new type. * ports -- This is the list of connections. * args -- The arg list is optional. If left out, the arg list is open. It accepts whatever it is fed.

2013-06-27T13:08:42-05:00 2013-06-27T13:08:42-05:00 2013-06-27T13:08:42-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:parse_top_item?rev=1372356522&do=diff

parse_top_item The function parse_top_item must be provided. Usually you can just copy this. /*--------------------------------------------------------------------------*/ void LANG_VERILOG::parse_top_item(CS& cmd, CARD_LIST* Scope) { cmd.get_line("gnucap-verilog>"); new__instance(cmd, NULL, Scope); } /*--------------------------------------------------------------------------*/

2013-06-27T13:25:57-05:00 2013-06-27T13:25:57-05:00 2013-06-27T13:25:57-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:ports?rev=1372357557&do=diff

parse, print ports Background Ports are the connections, how this particular instance is connected to the rest of the circuit. Paramsets do not have ports. In most languages, ports are nodes. “Through” ports such as currents are rarely supported. Nodes and through ports are stored in separate lists. As of when this is being written, only the Spice format supports through ports in any way, and even this is limited to just a few devices.

2013-06-27T13:06:47-05:00 2013-06-27T13:06:47-05:00 2013-06-27T13:06:47-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:simple_query_functions?rev=1372356407&do=diff

Simple query functions ~LANGUAGE() C++ rules require a virtual destructor when there are virtual functions. You need to define one as a tracing aid. It can be an empty function. ~LANG_VERILOG() {itested();} std::string name()const Return the name to use as a key to enable this language.

2013-06-27T12:51:24-05:00 2013-06-27T12:51:24-05:00 2013-06-27T12:51:24-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:top_level?rev=1372355484&do=diff

Top Level At top level, you need to include the header file. #include "gnucap/lang_base.h" If you want to be able to static link the plugin, or combine it with others, wrap it in an anonymous namespace. namespace { /*--------------------------------------------------------------------------*/ // all of your other code goes here /*--------------------------------------------------------------------------*/ } // close the anonymous namespace /*-----------------------------------------------…

2015-12-11T15:39:55-05:00 2015-12-11T15:39:55-05:00 2015-12-11T15:39:55-05:00 http://gnucap.org/dokuwiki/doku.php/gnucap:manual:tech:plugins:languages:type?rev=1449869995&do=diff

Implementation parse, print instance, paramset parse, print type Background It may seem redundant to parse the type again, because the type is already known. It was determined by find_type_in_string, then the type was looked up, and a new instance of that type was created.