All,

I am using Data::FormValidator to provide input checking/constraints/filters for my 
CGI::Application.

Data::FV makes it easy to code constraints on $B and $C, or to require $B and $C if $A 
exists by setting up rules contained in a hash structure. Like so...

#  snip

     dependencies   =>
           {  # If A is "N", make list of inputs required
              "A" => {
                   N =>  [ qw/
                          admin_contact_fk                            
+            
                          tech_contact_fk
                          billing_contact_fk
                         / ],
                     }
     },
     constraints => {  # check these inputs with these subs
                 dn_id       => 'OK_int',
                 foo         => 'OK_chars',
     },

#  snip

I would like to write a construct so that if Input $A = exists, then Input $B and $C 
have to meet certain constraints. If $A isn't one of the inputs, then the $B anc $C 
have no constraints

I don't see any way other way, using D::FV, than writing custom constraints that take 
in $A, $B, and $C to solve my problem. Is this true? 


=============================================================================
Fred Kleindenst                 [EMAIL PROTECTED]
Internet Platforms
310.302.3801 


-----Original Message-----
From: news [mailto:[EMAIL PROTECTED] Behalf Of Mark Stosberg
Sent: Tuesday, March 16, 2004 7:37 PM
To: [EMAIL PROTECTED]
Subject: [cgiapp] Re: prerun_mode warning


On 2004-03-16, Darin McBride <[EMAIL PROTECTED]> wrote:
> On March 16, 2004 1:04 pm, Erik Milosevic wrote:
>> prerun_mode generates a warning whenever it is used to switch a mode in
>> the cgiapp_prerun hook. This came up before, in the following messages:
>>
>> http://www.mail-archive.com/[EMAIL PROTECTED]/msg01018.html
>> http://www.mail-archive.com/[EMAIL PROTECTED]/msg01019.html
>>
>> The newest version (3.22) still generates this warning. Is there a reason
>> this behavior is still there? It doesn't seem useful to me, but I may be
>> missing something.
>>
>> If it just hasn't been gotten around to, I could submit a quick patch.
>
> As long as you're looking at patches, remove the other $^W use, too,
> for autoloads, for exactly the same reason.  It's a documented method
> of doing something, it shouldn't generate warnings.

I don't like these either. I'll plan to patch CGI::App for these myself.  
Documented functionality shouldn't produce warnings, IMO.

        Mark

-- 
http://mark.stosberg.com/ 


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/[EMAIL PROTECTED]/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/[EMAIL PROTECTED]/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to