[EMAIL PROTECTED] wrote:
dougm 2002/06/03 16:41:18
Modified:src/modules/perl mod_perl.c mod_perl.h
Log:
add MODPERL2 config define, as if the server had been started with -DMODPERL2
Revision ChangesPath
1.121 +10 -2
The otherthing is the test suite, which need to know which version we are
using and startup.pl need to decide to load Apache::Registry or
ModPerl::Registry. I currently check $ENV{MOD_PERL}, is there a better way
to decide, if we are running under mod_perl, something like
$ModPerl::MajorVersion
Doug MacEachern wrote:
On Tue, 4 Jun 2002, Stas Bekman wrote:
I haven't finished porting the registry family. When I'm done there will
be no need for Apache::compat to run ModPerl::Registry. Why would you need
to know whether you are running under Apache::Registry or
ModPerl::Registry? they
Doug MacEachern wrote:
On Tue, 4 Jun 2002, Stas Bekman wrote:
Meaning that we do want to be compatible with 1.x?
yes, wherever possible when it doesn't cause more trouble than it is
worth.
Should PerlFreshRestart be allowed then as NOOP so the same config can
be used for both
Doug MacEachern wrote:
On Mon, 3 Jun 2002, Herbert Rosmanith wrote:
sub trans($$) {
also, this needs to be:
sub trans : method {
which works with both 1.x and 2.x
5.005_03 inclusive?
__
Stas Bekman
On Mon, 3 Jun 2002, Herbert Rosmanith wrote:
aha. I had changed that to use Apache2::APR::Table(); and it worked.
you shouldn't have to do that. do you configure:
PerlModule Apache2
PerlModule Apache::compat
?
yes, I do.
$r-lookup_uri;
seems to be mising. Apache
with the latest httpd from cvs I get the following;
-c modperl_filter.c mv modperl_filter.o modperl_filter.lo
cc -I/home/ask/ap/modperl-2.0/src/modules/perl -I/home/ask/ap/modperl-2.0/xs
-I/home/ask/apache2/include -D_REENTRANT -D_GNU_SOURCE -DDEBUGGING
-fno-strict-aliasing
Herbert Rosmanith wrote:
by the way, I downloaded the latest snapshot from perl.apache.org
(modperl-2.0_20020604042309.tar.gz), but Apache::log_error was still
undefined there. Can I use these snapshots or would I have to use
cvs? (I am behind a firewall which doesnt allow me to do cvs
Herbert, this is already documented here:
http://perl.apache.org/release/docs/2.0/user/compat/compat.html#C_log_reason___
it says:
log_reason() has been replaced with a set of dedicated functions:
Apache::RequestRec::log_error(), Apache::ServerRec::log_error(),
Apache::Log::info() and
You want to load Apache::RequestRec and then it'll show up.
another issue: when I use Apache::RequestRec(); the module
will not start under modperl-1.0.
/herp
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Herbert Rosmanith wrote:
Herbert, this is already documented here:
http://perl.apache.org/release/docs/2.0/user/compat/compat.html#C_log_reason___
it says:
log_reason() has been replaced with a set of dedicated functions:
Apache::RequestRec::log_error(),
Herbert Rosmanith wrote:
You want to load Apache::RequestRec and then it'll show up.
another issue: when I use Apache::RequestRec(); the module
will not start under modperl-1.0.
why should it? It's a 2.0 module. If you want to have your startup file
work for both consider using:
=head2
You should use:
Apache-server-log_error(test3.pm::BEGIN);
if you don't have $r, or $r-log_error() inside the handler.
I don't think this is any different from 1.0
it is, because with 1.0, I can happily use Apache::log_error, which
I have done at numerous places.
package
Herbert Rosmanith wrote:
You want to load Apache::RequestRec and then it'll show up.
another issue: when I use Apache::RequestRec(); the module
will not start under modperl-1.0.
why should it? It's a 2.0 module.
you told me to use it ..
let me explain: I wrote a 1.0-module.
Herbert Rosmanith wrote:
Herbert Rosmanith wrote:
You want to load Apache::RequestRec and then it'll show up.
another issue: when I use Apache::RequestRec(); the module
will not start under modperl-1.0.
why should it? It's a 2.0 module.
you told me to use it ..
I thought you want
Herbert Rosmanith wrote:
You should use:
Apache-server-log_error(test3.pm::BEGIN);
if you don't have $r, or $r-log_error() inside the handler.
I don't think this is any different from 1.0
it is, because with 1.0, I can happily use Apache::log_error, which
I have done at numerous
[EMAIL PROTECTED] wrote:
-CGATEWAY_INTERFACE - is always set to something like: CCGI-Perl/1.1
+CGATEWAY_INTERFACE - is set to CCGI-Perl/1.1 for compatibility
+with mod_perl 1.x. The CMOD_PERL environment variable has existed
+since 1.17 and is recommended over checking the contents
+sub log_error {
+Apache-server-log_error(@_);
+}
+
yep, I have alread done this. however, with the latest cvs, apache-2
segfaults:
[Tue Jun 04 13:24:48 2002] [error] trans
[Tue Jun 04 13:24:48 2002] [error] SubEnvironment
[Tue Jun 04 13:24:48 2002] [error] trans
[Tue
Herbert Rosmanith wrote:
+sub log_error {
+Apache-server-log_error(@_);
+}
+
yep, I have alread done this. however, with the latest cvs, apache-2
segfaults:
[Tue Jun 04 13:24:48 2002] [error] trans
[Tue Jun 04 13:24:48 2002] [error] SubEnvironment
[Tue Jun 04 13:24:48
from include/http_log.h
/* APLOG_NOERRNO is ignored and should not be used. It will be
* removed in a future release of Apache.
*/
#define APLOG_NOERRNO (APLOG_LEVELMASK + 1)
we should probably remove it from constants and where it's used (in
aplog.pm test)
Greetings.
I am hitting a complex Registry application with a number of almost
simultaneous, long running requests
(WinNT SP6 - VC++6 SP3 - perl5.8.0 RC1 - latest dev snapshot for modperl -
httpd-2.0_20020530041218.tar.gz for apache - everything built debug - a few
date.t tests fail on nmake
Doug MacEachern wrote:
On Tue, 4 Jun 2002, Stas Bekman wrote:
BTW, Gerald, if you are using compat, you can still use the 1.0's
Apache::Registry. So you don't really need to conditional.
he does if 1.x is not installed.
True. I didn't think there was a possibility of not having 1.0
On Tue, 4 Jun 2002, Stas Bekman wrote:
5.005_03 inclusive?
one needs at least 5.6.0 to run 2.0
not concerned that 5.6.0 has no support for subroutine attributes.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
+1 on removing it.
On Tue, 4 Jun 2002, Stas Bekman wrote:
from include/http_log.h
/* APLOG_NOERRNO is ignored and should not be used. It will be
* removed in a future release of Apache.
*/
#define APLOG_NOERRNO (APLOG_LEVELMASK + 1)
we should probably remove it from
Doug MacEachern wrote:
On Tue, 4 Jun 2002, Stas Bekman wrote:
5.005_03 inclusive?
one needs at least 5.6.0 to run 2.0
not concerned that 5.6.0 has no support for subroutine attributes.
That's why I couldn't understand this comment of yours:
also, this needs to be:
sub trans :
On Wed, 5 Jun 2002, Stas Bekman wrote:
That's why I couldn't understand this comment of yours:
i don't understand what you don't understand.
also, this needs to be:
sub trans : method {
which works with both 1.x and 2.x
Did you mean something else?
no.
Gerald, I've started:
http://perl.apache.org/release/docs/2.0/devel/porting_from_1.x/porting_from_
1.x.html
which already covers some of the porting bits (like $mod_perl::VERSION).
$mod_perl::VERSION returns 1.9903, which is the same or similar then
$ENV{MOD_PERL} which I using right now,
On Tue, 4 Jun 2002, Gerald Richter wrote:
$mod_perl::VERSION returns 1.9903, which is the same or similar then
$ENV{MOD_PERL} which I using right now, but you need to split it with a
regex and compare, and a 1 before the point is mod_perl 2 if after the point
it start with 99, not very
On Tue, 4 Jun 2002, R Blake wrote:
doug,
it turns out that the troubles building modperl2 on OSX (at least for me
) turned out not to be (directly) PERL options related, but rather
required an update to libtool-1.4d ..
i've now successsfully built modperl2 (_20020531163044 )
Well, it is 88x31, like you asked. It's too long, that's why it looks
small when compressed to 88 pixels. That's also why I created the other
one, which makes the modperl text bigger.
True. But you lost the cogs in the bigger one. At least I don't see them.
Finally:
Alternatively, we also
[subject change]
Per Einar Ellefsen wrote:
also if I don't know what modperl is, I'd never understand from the
message on the banner (I know it's easy to criticize, as I didn't do one
:). So need some ideas here if you agree with me. Also some graphics will
make the banner more attractive, anybody
Most likely mod_perl 2.0 versioning will be using triplets (2.0.xx), and
even though that wasn't the case with the first mod_perl generation,
please try to refer to 1.x as 1.0 and 2.0.xx as 2.0 in the docs. This
convention makes the text easier to read, especially in the text which
is full of
Hi!
In download/docs, the shell is represented by
ai%
The attached patch removes the ai part to conform with the style guidlines.
That is, I thought it should be %. But in admin/style.pod, the opposite is
stated, i.e.
ai% ls -l
So what's correct?
I'll vote for
%
--
D_OMM
Thomas Klausner wrote:
Hi!
In download/docs, the shell is represented by
ai%
The attached patch removes the ai part to conform with the style guidlines.
That is, I thought it should be %. But in admin/style.pod, the opposite is
stated, i.e.
ai% ls -l
So what's correct?
I'll vote for
%
At 20:35 04.06.2002, Thomas Klausner wrote:
Hi!
In download/docs, the shell is represented by
ai%
The attached patch removes the ai part to conform with the style guidlines.
Thanks Thomas, applied.
That is, I thought it should be %. But in admin/style.pod, the opposite is
stated, i.e.
ai% ls
Hi!
On Wed, Jun 05, 2002 at 02:47:17AM +0800, Stas Bekman wrote:
I'd prefer to have some short prefix in prompt.
%
works fine, but not
#
That's right. I forgot about that.
If there is a strong opinion not to use this kind of prompt we can
change it. Of course in either
Hi!
Two more very small patches:
- src/contribute/maillist.pod
changed is the mailing lists to are the mailing lists.
Although I'm not sure about this, but in german there is a correlation
between the number of the subject and of the verb, and I think it's the same
in english...
-
At 21:00 04.06.2002, Thomas Klausner wrote:
Hi!
Two more very small patches:
- src/contribute/maillist.pod
changed is the mailing lists to are the mailing lists.
Although I'm not sure about this, but in german there is a correlation
between the number of the subject and of the verb, and I think
Thomas Klausner wrote:
Hi!
On Wed, Jun 05, 2002 at 02:47:17AM +0800, Stas Bekman wrote:
I'd prefer to have some short prefix in prompt.
%
works fine, but not
#
That's right. I forgot about that.
If there is a strong opinion not to use this kind of prompt we can
change it. Of course in
At 21:30 04.06.2002, Stas Bekman wrote:
Thomas Klausner wrote:
If there is a strong opinion not to use this kind of prompt we can
change it. Of course in either case we should be consistent, which is
not the case now.
ai% and ai# are OK for me, I only thought that we use only % and #.
Or, what
Per Einar Ellefsen wrote:
At 21:00 04.06.2002, Thomas Klausner wrote:
Hi!
Two more very small patches:
- src/contribute/maillist.pod
changed is the mailing lists to are the mailing lists.
Although I'm not sure about this, but in german there is a correlation
between the number of the subject and
At 21:42 04.06.2002, Stas Bekman wrote:
that's not good. consider:
% perl Makefile.PL ...
% make
root# make install
this looks much nicer:
ai% perl Makefile.PL ...
ai% make
ai# make install
Root prompts are pretty uncommon. And the fact is, we're already using %
without the ai. Let's
Hi!
On Tue, Jun 04, 2002 at 09:54:46PM +0200, Per Einar Ellefsen wrote:
At 21:42 04.06.2002, Stas Bekman wrote:
this looks much nicer:
ai% perl Makefile.PL ...
ai% make
ai# make install
what about
user% perl Makefile.PL
user% make
root# make install
But, well, I don't
As I said to Stas some days ago, I would like to make some sort of order in
the tutorials section, thereby having different sections (as was the
initial idea about this i think).
So, what about these sections:
Templating (template comparison)
Application building (EToys article)
Tips Tricks
At 03:30 AM 06/05/02 +0800, Stas Bekman wrote:
this looks much nicer:
ai% perl Makefile.PL ...
ai% make
ai# make install
I'd rather see
stas%
Then you don't have to wonder what ai is, plus you will get more hits on
google. ;)
What I really like is an example of what directory
On Tue, 4 Jun 2002, Bill Moseley wrote:
At 03:30 AM 06/05/02 +0800, Stas Bekman wrote:
this looks much nicer:
ai% perl Makefile.PL ...
ai% make
ai# make install
I prefer not having any prompt to make cut'n'paste easier.
--
ask bjoern hansen, http://ask.netcetera.dk/ !try;
46 matches
Mail list logo
