Skip to main content

Misspelled Variables

Care to guess what happens when you execute the following PHP?
define('FOO', 'Hi');
print(FO);
It prints 'FO'.

I do believe PHP got this from Perl:
perl
print FOO . "FOO"; # Prints FOOFOO
It works even if you're strict:
perl -w
use strict;
print FOO . "FOO"; # Prints FOOFOO
Ruby behaves differently depending on whether you try to print an undefined variable/method or an undefined attribute:
irb
>> print a
NameError: undefined local variable or method `a' for main:Object
from (irb):1
>> print @a
nil=> nil
Python raises an exception:
python
>>> print a
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
NameError: name 'a' is not defined
In a compiled language, these sorts of errors would be caught at compile time. However, a compiled language would never let me do something like:
python
>>> var_name = 'a'
>>> locals()[var_name] = 'yep'
>>> print a
yep
This example is a bit contrived, but I've definitely done things like it.

Personally, I like the flexibility of a scripting language. I like it even more when there's a tool like pychecker that can catch these sorts of errors. However, just because a scripting language doesn't have a compilation step that can catch stupid spelling mistakes doesn't mean it should accept them at runtime. I'd much rather deal with an exception than spend half an hour fighting a bug caused by a spelling error!

As a general rule, I think software should fail fast rather than glossing over bugs that will surely cause trouble later. I can handle the exception if I need to, but what I can't handle is a silent bug.

Comments

Mike Hansen said…
Your locals() example in Python only works because in the interpreter, you have that

>>> locals() is globals()
True

In general, the locals() is not modifiable in the way that globals() is.
Anonymous said…
Python lint catches this type of error.
Anonymous said…
it isn't really silent. You'll get an error in your logs:

PHP Notice: Use of undefined constant FO - assumed 'FO' in /data/sites/kai/warn.php on line 3
Anonymous said…
Variables (scalars) are prefixed by a $ in Perl:

~$ perl -Mstrict -e 'print $FOO . "FOO"'
Global symbol "$FOO" requires explicit package name at -e line 1.

I believe in PHP it's similar.
Anonymous said…
It's still a valid concern if you're using Perl constants.
$ perl -Mstrict -we 'use constant {FOO => "foo"}; print FO . "bar"'
FObar
Anonymous said…
Why do you think you could never do:

>>> var_name = 'a'
>>> locals()[var_name] = 'yep'
>>> print a
yep

In a compiled language? Isn't it more a type issue that compiled vs interpreted one?

If the language allows to store variables with different types in a list, I don't see why it won't work.
Mark Hughes said…
In Java:

Point obj = new Point(1, 2);
String varname = "x";
Object x = obj.getClass().getField("x").get(pt);
System.out.println(x); // prints 1


In Objective-C:

id obj = [[[MyPoint alloc] initWithX:1 y:2] autorelease];
NSString varname = @"x";
id val = [obj valueForKey:varname];
NSLog(@"%@", val); // prints 1

Compiled languages are only a problem if they lack true object-oriented features like metaclasses, reflection, and dynamic class loading (i.e., C, C++).
Anonymous said…
The Perl isn't a bug. It is doing exactly what it was designed to do. You are feeding it a list. In your case a list that you concatenate together. Perl "sees" that and good or bad does the assumption that you actually meant to concatenate that together as a list.

my $FOO = 'hello';
print FOO;

Name "main::FOO" used only once: possible typo at p.pl line 2.
p.pl syntax OK

my $FOO = 'hello';
print $FO;

Name "main::FO" used only once: possible typo at p.pl line 2.
p.pl syntax OK
jjinux said…
> In general, the locals() is not modifiable in the way that globals() is.

Right you are!
jjinux said…
> it isn't really silent. You'll get an error in your logs:

Yes, but why would I look in the logs if it doesn't show an error on the screen? Do most PHP programmers tail -f their logs in a terminal window while developing? That would make sense, but I've never done it.
jjinux said…
greg:
>In a compiled language? Isn't it more a type issue that compiled vs interpreted one?

It's not just that I'm storing stuff in a hash, it's that I'm creating new local (or actually global) variables on the fly. In C, you can't read in the name of a local variable from STDIN and then define that global variable on the fly.
jjinux said…
Mark:
> Compiled languages are only a problem if they lack true object-oriented features like metaclasses, reflection, and dynamic class loading (i.e., C, C++).

Great comment! Yes, reflection and dynamic class loading are two things I love dearly.
jjinux said…
aflury:
> It's still a valid concern if you're using Perl constants.

Great comment.

anonymous:
> The Perl isn't a bug.

I didn't say it was a "bug". I just disagree with the design decision. I'm glad that the cases you showed work. The case that I showed and the case that Andrew showed don't. Thanks for the comment :)
jjinux said…
> Variables (scalars) are prefixed by a $ in Perl:

Ugh, silly me. And to think I used to code in Perl! Too many languages leads to too much confusion ;)

Thanks.
Brandon L. Golm said…
IIRC, I think what you are seeing in Perl is that FOO is filehandle portion of the glob *FOO. When you treat this in scalar context, you get its name (which happens to be what you typed).

That way, the following thing works:

$x = FH;
$line = <$x>;

$ perl
print FOO BAR;
Can't locate object method "FOO" via package "BAR" (perhaps you forgot to load "BAR"?) at - line 1.

So it's not being treated as a string. It's just a coincidence really.
jjinux said…
> So it's not being treated as a string. It's just a coincidence really.

Thanks for setting me straight, Brandon :)

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p