> Ok, so I've installed 2.0b5 now, and here's the first problem. Is [$ var
> $] not valid any more? I have that on line 1 of one of my subroutine
> files, executed using Execute ({object => ...}). I get the following
> error: (this is using EmbperlObject)
>
> [1410]ERR: 24: Error in Perl code: 'undef' is not a valid variable name
> at /www/vhosts/www.crazyguyonabike.com/htdocs/Core.epl line 1
> \<br\>\ \ \ \ BEGIN failed--compilation aborted
> (in cleanup) 'undef' is not a valid variable name at
> /www/vhosts/www.crazyguyonabike.com/htdocs/Core.epl line 1
> \<br\>\ \ \ \ BEGIN failed--compilation aborted
> at /www/vhosts/www.crazyguyonabike.com/htdocs/Core.epl line
> 1.
>
> I tried adding an actual variable, e.g. [$ var $xxx $], but same error.
Oops. Looks like I was editing the wrong file here. I have Core.epl in
another virtual host, and was trying this on the wrong version. The [$
var $xxx $] makes the error go away. I guess the question still stands,
though - should [$ var $] by itself work? Is this a bug or a feature?
Apologies for the confusion.
(sound of hand repeatedly slapping forehead)
/Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
