Skip site navigation (1) Skip section navigation (2)

Re: PL/Perl embedding string common elements

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-patches(at)postgresql(dot)org
Subject: Re: PL/Perl embedding string common elements
Date: 2005-08-21 02:29:37
Message-ID: 19128.1124591377@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Every perl module whose author wants strict mode (and they all should) 
> has to carry such a declaration, so in a sense we'd just be doing what 
> perl itself does, and by trying to provide a global switch we're being 
> unperlish.

You missed my point.  I wasn't objecting to having the global switch,
only to the fact that turning it on and off doesn't do what a rational
person would expect.  If it's going to advertise itself as USERSET then
it darn well ought to be settable.

The idea of loading the strict module unconditionally seems ok to me,
if we can work out a way of making it apply or not apply to individual
function compilations.  From what you were saying, perhaps it would
work to implicitly add "strict->import();" when use_strict is enabled?

			regards, tom lane

In response to

Responses

pgsql-patches by date

Next:From: Andrew DunstanDate: 2005-08-21 02:49:32
Subject: Re: PL/Perl embedding string common elements
Previous:From: Andrew DunstanDate: 2005-08-21 02:18:21
Subject: Re: PL/Perl embedding string common elements

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group