Re: optUndefToEmptyValue off, and multipart/form-data in 1.3.3

2002-07-25 Thread Gerald Richter
> I don't have optUndefToEmptyValue set, so the default behavior is > that empty items aren't put in %fdat. However when I changed my form > type to multipart/form-data, the the behavior changed. Now are > inserted in %fdat. Yes, that's inconsitent, but it's the way it is... To get the old beh

Re: Stary brackets in Embperl vs. EmbperlObject ?

2002-07-25 Thread Gerald Richter
> > If I use the metacommands dollar-brackets, though, all is fine. Problem is, > however, that I unfortunately had the time to get used to PHP's way of > interweaving with HTML with only one kind of delimiter and, moreover, I'd > prefer to use clean Perl, so that I'd even drop EmbperlObject for s

Re: embperl unlink problem...

2002-07-25 Thread Gerald Richter
Hi, first of all the mailing list address is [EMAIL PROTECTED] I'm having problem with the UNLINK PERL command under embperl... This is my example code, copy works, rename works, but unlink no... I can't figure out what it's going on... Can someone help me? Thanks The on

Re: Execute

2002-07-25 Thread Gerald Richter
> It seems to work in some fashion with Embperl Meta Subs.. > > Is it by design that it seems not to function with perl subs? Am I doing > something wrong? :-( Is there anyway to make it function with perl subs? > It also works with perl subs, but you either need to tell Execute that you are lo

Re: using a diffrent EMBPERL_OBJECT_BASE

2002-07-25 Thread Gerald Richter
> > I get the error: > Syntax error on line 11076 of httpd.conf: > Invalid command 'EMBPERL_OPTIONS', perhaps mis-spelled > or defined by a module not included in the server > configuration > I guess you have a ClearModuleList directive somewhere in your httpd.conf. Embperl 2.0b8 configuration do

Re: Execute

2002-07-25 Thread Gerald Richter
> > In the 1.3 docs it's laid out pretty well here: > > http://perl.apache.org/embperl/pod/doc/doc13/HTML/Embperl.-page-3-.htm#sect_ 4 > > I'm not sure if there's an equivalent section in the 2.0 docs yet. > I am just in process of rewriting this part of the docs for 2.0 and have removed the old

Re: Deep Recursion

2002-07-25 Thread Gerald Richter
> > When I do this, it appears as if it is not even processing the [* *] > sections. Embperl subs must be defined before they are used in 1.3.4 (this isn't necessary in 2.0 anymore), which is not the case in your example. When you move the sub before the call of the sub it should work. > Does i

optUndefToEmptyValue off, and multipart/form-data in 1.3.3

2002-07-25 Thread Kee Hinckley
I don't have optUndefToEmptyValue set, so the default behavior is that empty items aren't put in %fdat. However when I changed my form type to multipart/form-data, the the behavior changed. Now are inserted in %fdat. -- Kee Hinckley - Somewhere.Com, LLC http://consulting.somewhere.com/ I'm no

Stary brackets in Embperl vs. EmbperlObject ?

2002-07-25 Thread Adrian Ghizaru
Hello all! First of all, here are the relating parts of my httpd.conf: PerlModule HTML::Embperl PerlSetEnv EMBPERL_FILESMATCH "\.html$" PerlSetEnv EMBPERL_DEBUG 9222 # dbgMem + dbgEval + dbgAllCmds + dbgLogLink PerlSetEnv EMBPERL_OPTIONS 16 # disables pre-processing of perl code to r

embperl unlink problem...

2002-07-25 Thread Gerardo Schimpf
Hi, I'm having problem with the UNLINK PERL command under embperl... This is my example code, copy works, rename works, but unlink no... I can't figure out what it's going on... Can someone help me? Thanks :+) embperl code: [- use File::Copy; $imbox="/var/www

Re: Compatability issue or just bad code

2002-07-25 Thread Ed Grimm
Disclaimer: I've never used Embperl 2; everything I know about it, I've gotten from reading this list. This is why I didn't remember this off-hand... and I could be somewhat off on the particulars. Ah, you're right. [+ +] blocks now have more strict requirements. You may get it working again

Re: Compatability issue or just bad code

2002-07-25 Thread Aaron Johnson
On Thu, 2002-07-25 at 10:21, Ed Grimm wrote: > Bad code. SELECTED should be quoted. As you have it here, perl > searches for a keyword SELECTED, and if it finds it, it uses whatever it > finds. Otherwise, it treats it as a string. You want it to always > treat it as a string. I tried it with

Re: Compatability issue or just bad code

2002-07-25 Thread Ed Grimm
Bad code. SELECTED should be quoted. As you have it here, perl searches for a keyword SELECTED, and if it finds it, it uses whatever it finds. Otherwise, it treats it as a string. You want it to always treat it as a string. Ed On 25 Jul 2002, Aaron Johnson wrote: > I was digging up some old

Compatability issue or just bad code

2002-07-25 Thread Aaron Johnson
I was digging up some old code and thought I would run it through 2.08b, I was aware of the foreach with no parentheses change, which this code had, but this block of code now throws an error as well: [+ if ($result1->[$count][3] eq "Regular After") {SELECTED} +] It provides a dynamic "selected"