ist on outputting "correct" code. After all, the clients
must be fixed ;->
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
Stas told me to forward my mail to the list, since there was a large
discussion about it. Since I now see that this seems to have been a kind
of dispute and not an ommision I'll provide references to the standards
below.
- Forwarded message from Marc Lehmann <[EMAIL P
eed here, but rather
about correctness, namely that I need ^/admin which shouldn't match at all
in a Location directive.
Thanks a lot for your reply!
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
same problem with
apache-1.3.14 and mod_perl-1.24 I upgraded to apache-1.3.17 and modperl
from cvs but the symptoms didn't change so I guess it might not be a bug
but rather some misunderstanding on my side :(
--
-==- |
==-- _
case).
So either the documentation or the implementation is in error. I would
prefer if the implementation were in error ;)
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Le
ocumented one, a way that breaks modules that work fine under the
documented mechanism, does not magically turn recommended code practises
into broken code practises.
--
-----==- |
==-- _ |
---==---(_)__ __ __
djust myself to the tone on (and around) the modperl
mailinglist.. Next time I will simply ignore most of the responses.
--
-==- |
==-- _ |
---==---(_)_
ave rather good arguments on the basis of
the perl language and protgramming, not because mod_perl does some very
undocumented things differently to perl itself.
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
at works only when called from
perl sections or also form perlrequire? (Hmm, I'll just try it out and assume
it's supported if it works ;)
--
-==- |
==-- _ |
ng
globals with Apache::Registry.
So I guess yes, I was being over-defensive. I'm sorry.
--
-==- |
----==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTEC
don't have a load-balanced cluster at your disposal...
*) It's also more disruptive ;)
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +
loading time. This, however,
is an incompatibility from mod_perl to standard perl, not "broken".
What is broken is the notion of "deleting from INC" is equivalent to
"unloading a module".
--
-==-
alking about perl then.
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=/_/_//_/\_,_/
27;s direct followup discussion about perl to private mail, thanks)
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
R1 safe?
(Sorry, so many questions.. :)
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=/_/_//_/\_,_/ /_/\_\
> new $x.
You cannot redefine closures as well.
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
rt. Old code and
variables are not cleared and might interfere with your module. Avoiding
lexical variables at global scope and not referencing subs before
declaration/definition is therefore recommended.
--
-==- |
art from patching _every_ module with a hack like
the one I posted)?
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMA
PERL_AUTHZ=1
PERL_TYPE=1
DO_HTTPD=1
=
Am I the only one who thinks that
{
my $x = ...;
sub the_only_function_using_x {
}
}
is cleaner then using a global variable? Heck,
ndle is the reparsing of my modules :(
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
een since apache-1.3.9).
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
sub yyy { $v }
--
-==- |
==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
On Tue, May 23, 2000 at 12:56:28AM -0500, Autarch <[EMAIL PROTECTED]> wrote:
> On Tue, 23 May 2000, Marc Lehmann wrote:
>
> > stable (mod_perl really is very unstable for large applications). Apart
>
> Wow, I wish you'd warned me before I did several large
uot;60feafc16b887e7fcfcf1814590ee576e908197c7d31a9fd13e25cb54f636b70",
pappdb=> "DBI:mysql:papp",
checkdeps => 1,
);
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
cessary).
Thanks a lot for any feedback ;)
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
25 matches
Mail list logo
