hello, if I can still contribute to this topic, I suggest you never use simlinks. We experienced very bad maintenance problems at a customer : when copying new files through FTP, the simlinks were often erased or overwriten. And this occured on every upgrade of the scripts. This would not occur with a simple and stable include_path setting. Moreover, one can set the include_path dircetly from PHP, allowing for example 2 applications to define their own include_path. Finaly, simlinks are not available on win32 platforms. So, the include_path should be more stable (considering FTP) and more flexible than simlinks. Vincent Dupont Ausy Belgium -----Original Message----- From: Richard Lynch [mailto:ceo@xxxxxxxxx] Sent: Sat 1/6/2007 0:17 To: Karl Pflästerer Cc: php-general@xxxxxxxxxxxxx Subject: Re: Question regarding include() and symlinks to directories On Thu, January 4, 2007 2:47 pm, Karl Pflästerer wrote: > In my opinion include() should respect symlinks to directories and not > dereference them before finding the file to include. Or am I wrong > here? > The PHP version is 5.1.6 (will soon be updated). WHOOPS! My fingers slipped and I keyboarded to "Send" button. SORRY! ... and use full pathname when you go to read a file. Anything else is more like playing an Adventure Game than Programming. I can see arguments both ways for when to work out the symlink, so you'd have to take this up with Internals to get a change made... -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some starving artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
