On Tue, 2003-09-23 at 07:47, Jay Blanchard wrote: > [snip] > The example that I'm really trying to do might be too complicated for > presentation here, but here's a simplified version. > > Take the shell script "helloWorld.php": > > #!/usr/local/bin/php -q > <?PHP print "\nHello World!"; ?> > [/snip] > > I could not replicate your problem on a 4.2.n or 4.3.n box but I will > say this concerning shell scripts (although the rpoblem only occured on > the 4.3.n box)...you should always have at least one blank line between > the bash and the start of the code. As long as that blank line existed I > had no problems on either box. I know that this is not much help, but I > did attempt to replicate your problem (only the paths were changed) and > these were my results.
I've never had a problem with not putting an extra blank line between binary path and the actual script. Actually I would say that would break the output since an extra line would be printed in the case of a PHP script. Cheers, Rob. -- .------------------------------------------------------------. | InterJinn Application Framework - http://www.interjinn.com | :------------------------------------------------------------: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `------------------------------------------------------------' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
