Re[2]: [Help-gnucap] Using hash symbol (#) in a variable

[gserdyuk]

Hello ,

I just tried "#" in device name, net name and param name

circuit:
---------------------------------------------------------
* hash in names

.param RSH=50k
.param R# = 50K

* hash in dev names
r1   1  0  50k
r#   1  0  50K

* hash in node names
r##  1  #1 50k
r3#  #1 0  RSH

* has in params
R4   1  2  R#
R5   2  0  50k

v1   1  0  dc 2

.list
.print op v(*)
.op 
.end
---------------------------------------------------------
results:
---------------------------------------------------------
* hash in names
r1 ( 1 0 )  50.K
r# ( 1 0 )  50.K
r## ( 1 #1 )  50.K
r3# ( #1 0 ) RSH()
R4 ( 1 2 ) R#()
R5 ( 2 0 )  50.K
v1 ( 1 0 )  DC  2.
#           v(#1)      v(1)       v(2)       v(r1)      v(r#)      v(r##)     
v(r3#)     v(R4)      v(R5)      v(v1)     
 27.        1.         2.         1.         2.         2.         1.         
1.         1.         1.         2.        

---------------------------------------------------------
so far it does work in param names - v(r1)=1, which is 1/2 of v(v1)=2
so r#() has to be = 50k


Cheers
Gena

Sunday, July 19, 2009, 8:01:17 AM, you wrote:


c> I understand now. It is far more important to us to allow the "#" in net and
c> device names than parameters. We will work around the issue.


c> al davis-13 wrote:
>> 
>> On Saturday 18 July 2009, cliffnotes wrote:
>>> It would be nice to support 1 non-alphanumeric character to
>>> allow us to allow us a hook for our tool to do some advanced
>>> things. It can be an "@" or "|" or whatever, but "#" is a
>>> character that I believe I have seen in the past used legally
>>> in several simulators. Can you enhance the simulator to allow
>>> "#" to be legal within the device name, net name, or param
>>> name?
>> 
>> Those symbols do work in device names and net names.
>> 
>> There is an issue with param names because of param expressions.  
>> Those characters can have meanings of their own in expressions.  
>> For example "foo|bar" .. is likely to mean "foo or bar".
>> 
>> Param expressions are known to have issues.  Fixing it, or even 
>> documenting it properly, requires further study.  I think any 
>> problems there will come out as testing and debugging of 
>> expressions is completed.
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Help-gnucap mailing list
>> address@hidden
>> http://lists.gnu.org/mailman/listinfo/help-gnucap
>> 
>> 




-- 
Best regards,
 Gserdyuk                            mailto:address@hidden