Zugg Software :: View topic

Adept Joined: 20 Jul 2004 Posts: 268

Something that I noticed while working on a reporter
if you have a #function and look at it in settings it gives the same icon as a #var.
And when u export it it calls it a #var

#FUNCTION addcommas {%subregex(%1,"(\d(1,3)?(?=(?>(?:\d{3})+)(?!\d))|\G\d{3}(?=\d))","%%1,")}
#FUNCTION padleft {%concat( %repeat( " ", %eval( %3-%len( %1))), %1)}

export:
#VAR addcommas {%subregex(%1,"(\d(1,3)?(?=(?>(?:\d{3})+)(?!\d))|\G\d{3}(?=\d))","%%1,")}
#VAR padleft {%concat( %repeat( " ", %eval( %3-%len( %1))), %1)}

And then when you import them it comes out wrong and says that both of them have values of %1

How the heck do you get it NOT to export as a #var.
It just makes it hard to export the script to send to someone if you forget that the conversion happens.

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

You can't and it sucks because everytime I export my scripts I have to go through and change the #VAR to #FUNC. But the only differance between #VAR and #FUNC is how its expanded/evaluted when it is created.

Both of these are the same
#VAR name "" //doesn't expand
#FUNC name {} //doesn't expand

however normal Variable operation is this
#VAR name {} //does expand

Adept Joined: 20 Jul 2004 Posts: 268

sooo....meaning that rather than have them as #functions I can put them in #vars if i have them surrounded by {}'s?

SubAdmin Joined: 18 Nov 2001 Posts: 5182

In state of fact, #FUNCTION's are a specialized type of #VARIABLE's. The import and export abiltities are meant to operate in verbatim mode. However the subtle difference between #FU and #VAR is lost. This has been a point of contension betwixt Zugg and I for a long time, and has actually lead to me avoiding the use of #FUNCTION entirely. In general if you export a script that makes use of #FUNCTION's you should correct the exported version to assure that the script is properly importable.

Posted: Thu Jun 30, 2005 4:31 pm