[prev] [thread] [next] [lurker] [Date index for 2006/12/15]
On Fri, 15 Dec 2006 16:59:57 +0000, Martin Ebourne <lists@xxxxxxx.xx.xx>
wrote:
> "H.Merijn Brand" <h.m.brand@xxxxxx.xx> wrote:
> > As long as it takes? How would you think Dutch/Polish/French/Russian/...
> > would like to beat you back with all the `English' verbs in their script
> > that uses variable with native-language names?
>
> How long has perl allowed you to localise all the builtins?
Every (programming/scripting) language has reserved words. Lets not start
hatred threads about that, then I'd start with flogging Oracle.
> And even if it did, what about all the CPAN modules - all the ones
> I've ever seen use english names.
They are not in the CORE package, and thus optional to install.
> While I can understand the problem for non-native english speakers
> it's an endemic problem to any software at that level (as opposed to
> the UI level). I am not aware of any language that's translated in
> this way (although there's bound to be at least one, please correct me).
>
> So how is having english names for builtin variables worse than having
> english names for builtin functions? Having variables named after
> whatever key was spare on the keyboard at the time is not a good
> design decision.
$" is named because of it's functionality of interpolation within a
double-quoted string. Very logical. Very easy to remember. Not just
a random choice of the available keys.
Same for many others ($, $? $; $0 $$), but I agree that not all are
logical, esp the $^ variables make me need my QuickRefGuide
--
H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using & porting perl 5.6.2, 5.8.x, 5.9.x on HP-UX 10.20, 11.00, 11.11,
& 11.23, SuSE 10.0 & 10.1, AIX 4.3 & 5.2, and Cygwin. http://qa.perl.org
http://mirrors.develooper.com/hpux/ http://www.test-smoke.org
http://www.goldmark.org/jeff/stupid-disclaimers/
There's stuff above here
Generated at 22:02 on 27 Dec 2006 by mariachi 0.52