NYCPHP Meetup

[Brian Pang]

sure, then I decided I don't like working with other people so much...
;)

point well taken...

only a big, meanie would try to keep a dozen puppies in one cardboard box.


> *LOL* ever worked in a big ill-defined multi programmer project? or
worse...
> multiple designers?
> 
> really though getting my designers to keep up a naming scheme on their
> templates is like trying to keep a dozen puppies in a cardboard box.
> 
> > -----Original Message-----
> > From: Brian Pang [mailto:bpang at bpang.com]
> > Sent: Friday, 09 May, 2003 7:30 AM
> > To: NYPHP Talk
> > Subject: RE: [nycphp-talk] Differences btw include and require ?
> > 
> > 
> > I would always use _once unless I specifically need to repeat 
> > something...
> > 
> > good point about continuing processing on a not found error.. but why
> > would I try to include/require a file that doesn't exist? :)
> > 
> > 
> > > include_once... solves 2 scripts calling the same include
> > > 	plus you can keep processing on a fail for a cleaner error 
> > > 
> > > > -----Original Message-----
> > > > From: Brian Pang [mailto:bpang at bpang.com]
> > > > Sent: Friday, 09 May, 2003 7:21 AM
> > > > To: NYPHP Talk
> > > > Subject: Re: [nycphp-talk] Differences btw include and require ?
> > > > 
> > > > 
> > > > I use require when I'm just calling in function libraries 
> > and includes
> > > > like a server-side include.
> > > > 
> > > > But otherwise, they do seem to behave similarily, don't they..
> > > > 
> > > > 
> > > > > What are the differences?  Personally, I always use 
> > include_once().
> > > > > 
> > > > > Thank you.
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> 
> 
> 
> --- Unsubscribe at http://nyphp.org/list/ ---
> 
> 
> 
>