>> the horse is back from the dead!
>
>huh?
inside joke.
> Why? If nested tables can do the work, i won't bother learning how layers
> work...
um, I mean in your application design, not your html.
>> I don't like to do database connections when I've already output markup,
>> what if something goes wrong, or I want to do a redirect, etc?
>
> If something goes wrong -> It's the DBA fault. :-)
hehe
in a production encironment: agh!
>> I like to access functions in "DB Object" files - those functions return
>> results in arrays which I can pass into markup.
>>
>> Makes the code a _helluvuh_ lot more maintainable.
>
> I'm pretty comfortable programming directly with OCIwhatever() functions
> directly in the main code, that's it.
ok, go ahead. that in my opinion is not the way to go, especially for
portability and reuse of code... it's also the quick route to hair-pulling
if you QA your code...
> In other words, i don't need to make my code more maintainable because i'm
> comfortable with maintaining it right now.
well, then why bother arguing the point?
my opinion only matters if you care about it?
otherwise I'm just babbling. (ohh I see some responses to this one)
>> True, but why not just bitch at macromedia until they include support for
>> PHP in ultradev?
>
> (Well, i haven't purchased dreamweaver either)
good, that means you're not using any diabolical visual tools :)
>> (plegh, visual authoring tools: a necessary evil)
>
> Why, when you have notepad.exe and a couple of browsers to test that the
> pages work properly?
whoa, dude.
that's scary. but do whatever you want!
-alex
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
