yeah, my wife gets a little defiant when I try to tie her
seriously, this is good stuff! And thanks to Jonathon for the perlmonks.org resource! New one for me.
mark>>> Chris Werner <[EMAIL PROTECTED]> 23-Feb-06 10:45:13 AM >>>
The other DBM db's: NDB for example, are similarly suppor
Check the archives for last week. There was much discussion on this.
The biggest way to to sep. work and presentation is to strictly
adhere to MVC principles
Anyways:
Names that people are happy with:
Template::Toolkit
Mason
HTML::Tem
Jonathan Vanasco wrote:
> on this topic, please forgive my ignorance...
>
> don't both those settings relate to mod_perl internals?
Oh, yes, very much internal indeed.
> i typically just to a
>
> use constant DEBUG__myvar => 1 ;
>
> and
> DEBUG__myvar && print STDERR "my debug cra
Hey all, just wondering what the "current" technology for templating
and mod_perl is? A few years ago it was embPerl and HTML::Mason and a
few years before that it was "pure" mod_perl, or running cgi's under
perl::register.
I'm thinking of redoing a couple of sites and was wondering if I'm
going
on this topic, please forgive my ignorance...
don't both those settings relate to mod_perl internals?
i typically just to a
use constant DEBUG__myvar => 1 ;
and
DEBUG__myvar && print STDERR "my debug crap"
in my code to handle debugging my apps. in one of the books, it said
"Thomas den Braber" <[EMAIL PROTECTED]> writes:
> my $req = APR::Request::Apache2->handle($r);
> $req->read_limit(6000); works fine
> $req->read_limit(8000); gives Conflicting information error
> If I don't set:
> print $req->read_limit(); gives 67108864
>
> Is there some hardcoded limit
Torsten Foertsch wrote:
> On Tuesday 21 February 2006 19:17, Geoffrey Young wrote:
>
>>>I need something like this:
>>>
>>>__END__
>>>= 2.2.0>
>>>AllowOverride AuthConfig Options=Indexes,FollowSymLinks
>>>
>>>
>>>Unfortunately, IfVersion is valid only from 2.0.56 on. Is there a
>>>workaround in mo
Tyler MacDonald wrote:
> You know what?
>
> The mod_perl people are freaking geniuses.
>
> This works:
>
>
> warn __FILE__, " - ", __LINE__, "\n";
>
That's a feature, actually. I am afraid it isn't documented
anywhere though, so +1 for finding this solution ;-)
A bonus point would be award
Boysenberry Payne wrote:
> I have a couple of question while installing MP2 over again.
>
> Do I have to enable MP_DEBUG and MP_TRACE in order to debug
> or trace; does that mean I'll be stuck with everything being debugged or
> traced?
MP_DEBUG means the compiled code will have debugging symbols
Stas Bekman wrote:
William A. Rowe, Jr. wrote:
What I'm trying (failing?) to point out is that on BSD and other platforms, if
they have a bug, they can munge *PERL*, not ApacheTest, not each and every perl
script which creates perl files, with an effective value of $Config{startperl}.
What yo
William A. Rowe, Jr. wrote:
[...]
$Config{sh}, $Config{perlpath}, and $Config{perl} comes from -this-
perl, right?
right
#/usr/bin/perl is a hardcode to an arbitrary perl installed at that
location.
What I'm trying (failing?) to point out is that on BSD and other
platforms, if
they have a
I have a couple of question while installing MP2 over again.
Do I have to enable MP_DEBUG and MP_TRACE in order to debug
or trace; does that mean I'll be stuck with everything being debugged or
traced?
Thanks,
Boysenberry
boysenberrys.com | habitatlife.com | selfgnosis.com
Stas Bekman wrote:
William A. Rowe, Jr. wrote:
I don't think the reporter understood the concept of
#!/usr/bin/perl
eval 'exec $Config{perlpath} -S \$0 \${1+"\$@"}'
if \$running_under_some_shell;
which is a noop under perl, and invokes a shell exec command under shell. Perl
never invokes t
Most of these non- mod-perl centric questions can be answered faster
with a lookup on perlmonks.org
oddly though, this list is bouncing today.
anyways, a quick search on gdbm on perlmonks likes to this node:
http://perlmonks.org/?node_id=405754
which links to this page from the camel
On Thu, Feb 23, 2006 at 10:27:35AM -0500, Mark Galbreath wrote:
> looks way cool - thx Chris. Does libgdbm come with perl distros? I
> notice the man page is already on my RH Enterprise 4 client. The reason
> I ask is that it is very painful to get the government to change anything
> on a server
The other DBM db's: NDB for example,
are similarly supported.
By the way tie's are not that hard once you
get used to them, but reuse and inheritance is defiantly the way to
go!
enjoy!
Christian
-Original Message-From: Mark Galbreath
[mailto:[EMAIL PROTECTED]Sent: Thursd
looks way cool - thx Chris. Does libgdbm come with perl distros? I notice the man page is already on my RH Enterprise 4 client. The reason I ask is that it is very painful to get the government to change anything on a server without lengthy and exhaustive QA. I'd like to start using stuff lik
man GDBM_File
-Original Message-From: Mark Galbreath
[mailto:[EMAIL PROTECTED]Sent: Thursday, February 23, 2006 7:08
AMTo: modperl@perl.apache.orgSubject:
TIE
I must be missing the point. In the 3rd
edition of the Camel Book, there is a passing reference in Chapter
1
>> In any case, this sort of hack should be left to the value of
>> $Config{startperl}
>> where it belongs, not a dozen workarounds in a dozen different projects.
>
>
> I'm not following you, how $Config{startperl} solves the problem of the
> long path, if just as you say it makes the script run
I must be missing the point. In the 3rd edition of the Camel Book, there is a passing reference in Chapter 14 that goes something like
You used to have to use dbmopen() but now you can use tie.
I am picking perl back up after 10 years and dbmopen() always worked great for me. I don't ca
I just upgraded from libapreq 2.06dev to 2.07 on a Windows 2003 server and I
get an error: Conflicting information if I set the read_limit above
67108864.
my $req = APR::Request::Apache2->handle($r);
$req->read_limit(6000); works fine
$req->read_limit(8000); gives Conflicting information
William A. Rowe, Jr. wrote:
I don't think the reporter understood the concept of
#!/usr/bin/perl
eval 'exec $Config{perlpath} -S \$0 \${1+"\$@"}'
if \$running_under_some_shell;
which is a noop under perl, and invokes a shell exec command under
shell. Perl
never invokes the exec ($running_un
22 matches
Mail list logo
