Re: [PATCH] Test that constant overloading is propagated into eval
On 12/26/05, Robin Houston <robin@xxxxxxxx> wrote:
> + # Check that constant overloading propagates into evals
As a further confirmation of the fact, the following one-liner (using
bigint and eval with strings) that used to output
$ perl -Mbigint -e "my $x = eval '1+2'; use
Data::Dumper; print Dumper $x"
$VAR1 = undef;
now outputs "$VAR1 = 3" as expected. No contortion to get a proper answer..
.
Relevant Pages
- Re: reading Perl syntax
... I'm really botching this up... ... 'file' => undef ... The Dumper code you supplied cause the $VAR1 section. ...
(perl.beginners) - Problems with InvokeMember()
... The example from MSDN works fine for strings,but it's not working for ... primitives like 'double' ... Type mtype = m.GetType; ... Prev by Date: ...
(microsoft.public.dotnet.csharp.general) - Re: PASSING VARIABLES...
... input the values for var1 and var2: ... So once the user fills in the form and hits submit, ... Prev by Date: ...
(php.general) - Re: Interfacing question
... include data in a gazillions forms, but fundamentally that are all bits ... a few strings, integers ... etc. that could easily be returned using a function call as var types ... Prev by Date: ...
(microsoft.public.vb.general.discussion) - Re: Boolschen Kontext forcieren
... > Funktion mit Namen "str" undef in einen Leerstring umwandelt, ... >>> Im Fall von Strings achte ich entweder darauf, ... Prev by Date: ... Next by Date: ...
(de.comp.lang.perl.misc) |
|
