One further note:
param(i) is indeed parsed differently by the compiler
than a custom function as long as there is a parameter
for the result of param(i) called in the statement.
This means:
put param(i)
works, but (with parameter)
put the visible of param(i)
yields an error.
Ralf
On 30.01.2009, at 04:54, Brian Yennie wrote:
Thomas,
He wasn't trying to get the handler name... but trying to help is
good =). It's actually an interesting piece of trivia that param(0)
will fetch the handler name. Similarly, $0 fetches the script name
for a CGI script...
It seems to me that param(i) is just parsed differently by the
compiler than a custom function. Something about the order of
evaluation changes. I wonder whether value(param(i)) would work? Or
just an echo function:
set the visible of echo(param(i)) to TRUE
function echo v
return v
end echo
Of course, the original workaround is pretty painless, luckily.
- Brian
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
