Fwd: [Help-gnucap] inline comment delimiter

[asomers (Bugzilla)]

Here's a thread that started out on gnucap-help:

What is the inline comment delimiter in gnucap, and what should it be?

According to the manual for V0.35, the delimiter is quote.  It doesn't
say whether that is single quote or double quote.

According to Al Davis, there are no inline comments in gnucap.

From experiment, it seems that ' starts a comment on my lines, but "
starts a comment on a .SUBCKT line.  Here is an example script that
illustrates both types of quote:
*Comment test
*On a .SUBCKT line, it seems that " is a comment delimiter
*But elsewhere it seems that ' is a comment delimiter
.SUBCKT Foo 1 2 "(IN
*This next line will not work if you uncomment it
*.SUBCKT Bar 1 2 '(IN
.ENDS Foo
R  1 2 1000
D1 2 0 DIODE1 ' a comment
V1 1 0 dc 1 ac 0
.MODEL DIODE1 D(IS=8.2592e-16 RS=10) ' a comment
.op

-Alan Somers


---------- Forwarded message ----------
From: al davis <ad211@...>
Date: Fri, Sep 11, 2009 at 9:52 AM
Subject: Re: [Help-gnucap] inline comment delimiter
To: help-gnucap@...


On Friday 11 September 2009, asomers@... wrote:
> It says that in section 1.4: Command Structure.  On my
>  system, it's at:
>  file:///usr/share/doc/gnucap/html/gnucap-man006.html#htoc5

That's the old manual, for the old stable version.   (0.35??)
There are a lot of changes in the development version, which is
getting close to ready for release as a stable version.

> So I guess I what you're saying is that I should just delete
>  those comments.  That will work, although it's sad to lose
>  information. Gnucap can definitely not read LTSpice models
>  as is.  There are many changes I have to make.

The best approach is to move over to the developer list
(gnucap-devel@...) and point out the problems there,
specifically so they can be addressed directly.


_______________________________________________
Help-gnucap mailing list
Help-gnucap@...
http://lists.gnu.org/mailman/listinfo/help-gnucap


_______________________________________________
Gnucap-devel mailing list
Gnucap-devel@...
http://lists.gnu.org/mailman/listinfo/gnucap-devel

[al davis-13]

On Tuesday 15 September 2009, asomers@... wrote:
> Here's a thread that started out on gnucap-help:
>
> What is the inline comment delimiter in gnucap,

It depends on the language plugin, but mostly it doesn't work.  
Let's fix it now.

Gnucap accepts several different simulation languages.  What is
the comment delimiter should depend on what language you are
using.

> and what
>  should it be?

With the language plugins, it is possible to have exact
compatibility with most other simulators, even the different
incompatible versions of Spice.

As it stands, compatibility isn't perfect, but Hspice and Eldo
have been treated as the "spice" versions for which the highest
compatibility is desired.

> According to the manual for V0.35, the delimiter is quote.
>  It doesn't say whether that is single quote or double quote.

That's unclear. .. The manual is being rewritten completely.  
The new version is on the wiki at:
http://gnucap.org/dokuwiki/doku.php?id=gnucap:manual

> From experiment, it seems that ' starts a comment on my
> lines, but " starts a comment on a .SUBCKT line.  

Several characters are accepted to start whole-line comments,
going back a long time when different versions of spice used
different characters.  Since there was no standard, accept all
of them.

I think it has converged to "*".  Correct me if I am wrong.

It is easy to change it to just about anything.  So, since the
example is Spice format ..  What do the different versions of
Spice do?

(Hspice, Pspice, NGspice, LTspice, Eldo, Multi-sim, Smart-spice,
.....)

There is another issue now ...  You can have parameter
expressions.  It looks like Hspice and Eldo want them in single
quotes.  Pspice appears to want curly braces.  What else is
there?

Another comment issue is how comments mix with extension lines.  
It seems to be different in different simulators.



_______________________________________________
Gnucap-devel mailing list
Gnucap-devel@...
http://lists.gnu.org/mailman/listinfo/gnucap-devel

[asomers (Bugzilla)]

It looks like the spice language plugin section of the development
version's manual is yet to be written.  Is there any place I can go
for more info on that?

On Tue, Sep 15, 2009 at 6:00 PM, al davis <ad211@...> wrote:

> On Tuesday 15 September 2009, asomers@... wrote:
>> Here's a thread that started out on gnucap-help:
>>
>> What is the inline comment delimiter in gnucap,
>
> It depends on the language plugin, but mostly it doesn't work.
> Let's fix it now.
>
> Gnucap accepts several different simulation languages.  What is
> the comment delimiter should depend on what language you are
> using.
>
>> and what
>>  should it be?
>
> With the language plugins, it is possible to have exact
> compatibility with most other simulators, even the different
> incompatible versions of Spice.
>
> As it stands, compatibility isn't perfect, but Hspice and Eldo
> have been treated as the "spice" versions for which the highest
> compatibility is desired.
>
>> According to the manual for V0.35, the delimiter is quote.
>>  It doesn't say whether that is single quote or double quote.
>
> That's unclear. .. The manual is being rewritten completely.
> The new version is on the wiki at:
> http://gnucap.org/dokuwiki/doku.php?id=gnucap:manual
>
>> From experiment, it seems that ' starts a comment on my
>> lines, but " starts a comment on a .SUBCKT line.
>
> Several characters are accepted to start whole-line comments,
> going back a long time when different versions of spice used
> different characters.  Since there was no standard, accept all
> of them.
>
> I think it has converged to "*".  Correct me if I am wrong.
>
> It is easy to change it to just about anything.  So, since the
> example is Spice format ..  What do the different versions of
> Spice do?
>
> (Hspice, Pspice, NGspice, LTspice, Eldo, Multi-sim, Smart-spice,
> .....)
>
> There is another issue now ...  You can have parameter
> expressions.  It looks like Hspice and Eldo want them in single
> quotes.  Pspice appears to want curly braces.  What else is
> there?
>
> Another comment issue is how comments mix with extension lines.
> It seems to be different in different simulators.
>
>
>
> _______________________________________________
> Gnucap-devel mailing list
> Gnucap-devel@...
> http://lists.gnu.org/mailman/listinfo/gnucap-devel
>

_______________________________________________
Gnucap-devel mailing list
Gnucap-devel@...
http://lists.gnu.org/mailman/listinfo/gnucap-devel

[al davis-13]

On Tuesday 15 September 2009, asomers@... wrote:
> It looks like the spice language plugin section of the
> development version's manual is yet to be written.  Is there
> any place I can go for more info on that?

Spice documentation, but that doesn't tell you the differences
in gnucap.  As I said, the manual is a work in progress, trying
to track code that is a work in progress.



_______________________________________________
Gnucap-devel mailing list
Gnucap-devel@...
http://lists.gnu.org/mailman/listinfo/gnucap-devel