On 2005.09.23, Daniel P. Stasinski [EMAIL PROTECTED] wrote:
Useless code, yes, but it should ns_eval correctly but does not.
set code set somevar {\$blah}
ns_eval $code#doesn't work
eval $code #works
Interesting -- does this work in 4.0.x but not in
On 2005.09.23, Daniel P. Stasinski [EMAIL PROTECTED] wrote:
Useless code, yes, but it should ns_eval correctly but does not.
set code set somevar {\$blah}
ns_eval $code#doesn't work
eval $code #works
To answer my own question:
server1:nscp 1
On Mon, 2005-09-26 at 13:27 -0400, Dossy Shiobara wrote:
On 2005.09.23, Daniel P. Stasinski [EMAIL PROTECTED] wrote:
Useless code, yes, but it should ns_eval correctly but does not.
set code set somevar {\$blah}
ns_eval $code#doesn't work
eval $code
On 2005.09.26, Daniel P. Stasinski [EMAIL PROTECTED] wrote:
If all I do is add a single # comment as the very first line to the same
script, it updates fine.
I has got to be in NSAdmin but I haven't been able to re-create the
error in anything other than the package itself.
No, I don't
On Mon, Sep 26, 2005 at 01:32:08PM -0400, Dossy Shiobara wrote:
Yes, this (kinda) makes sense -- if you look at the ns_eval code, it
double-evaluates the input script (which, seems to cause lots of
confusion and grief).
Uh, where and why does it do that exactly? I'm looking at
On Mon, 2005-09-26 at 15:09 -0400, Dossy Shiobara wrote:
No, I don't think it's NSAdmin. Rob Seeger should have a better
explanation as to why this bug is happening, I think. I'll try to dig
through my email, unless he beats me to it.
Ok, I can duplicate the bug now. Here is the code. Try
In the _ns_helper_eval proc (which ns_eval uses to actually execute
code), the line that actually runs the code is:
set code [catch {uplevel 1 [eval concat $args]} result]
The reason for this is that ns_eval, by design, can take it's inputs in
two different forms:
ns_eval set a 1
On Mon, Sep 26, 2005 at 04:27:19PM -0400, Robert Seeger wrote:
In the _ns_helper_eval proc (which ns_eval uses to actually execute
code), the line that actually runs the code is:
set code [catch {uplevel 1 [eval concat $args]} result]
The reason for this is that ns_eval, by design,
On 2005.09.26, Robert Seeger [EMAIL PROTECTED] wrote:
In the _ns_helper_eval proc (which ns_eval uses to actually execute
code), the line that actually runs the code is:
[...]
Thanks, Rob. Sorry to put you on the spot with this, but I know you
knew this better than me ...
So, I retract my
Useless code, yes, but it should ns_eval correctly but does not.
set code set somevar {\$blah}
ns_eval $code#doesn't work
eval $code #works
Daniel
--
| ---
| Daniel P. Stasinski |
10 matches
Mail list logo
