[FX.php List] The skinny on includes
dale.bengston at gmail.com
Wed Jun 22 16:22:09 MDT 2011
I use require_once for including classes such as FX.php: my pages will stop processing if vital classes are missing. I use include_once for headers and footers and things like that. I don't give much thought to microseconds of speed difference between include and include_once.
On Jun 22, 2011, at 4:56 PM, Anders Monsen wrote:
> I also use require_once, for the sake of functionality far more so than speed.
> Anders Monsen
> On 6/22/11 4:54 PM, Steve Winter wrote:
>> I always use require_once, since I only ever want to include anything once, and as anything I'm 'including' will contain essential functions, I need the entire thing to fail if it doesn't happen...
>> Sent from the iPhone of Steve Winter
>> Matatiro Solutions
>> steve at matatirosolutions.co.uk
>> +44 777 852 4776
>> On 22 Jun 2011, at 22:51, Bob Patin <bob at patin.com> wrote:
>>> So what about include vs. include_once? What do you use when you do FX apps?
>>> Longterm Solutions
>>> bob at longtermsolutions.com
>>> iChat: bobpatin
>>> FileMaker 9, 10 & 11 Certified Developer
>>> Member of FileMaker Business Alliance and FileMaker TechNet
>>> Expert FileMaker Consulting
>>> FileMaker Hosting for all versions of FileMaker
>>> PHP • Full email services • Free DNS hosting • Colocation • Consulting :
>>> On Jun 21, 2011, at 2:45 PM, Anders Monsen wrote:
>>>> There are other things to consider aside from speed.
>>>> include will continue after a fatal error, but require will die after a fatal error.
>>>> Anders Monsen
>>> FX.php_List mailing list
>>> FX.php_List at mail.iviking.org
>> FX.php_List mailing list
>> FX.php_List at mail.iviking.org
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the FX.php_List