[FX.php List] [OT] Bizarre comment behaviour

[Dale Bengston]

Hmm, I was going to suggest that! I had a similar experience with a "gremlin" choking a Windows server. The script worked fine on Macs. The character was not visible in the script.

In November, I had a Windows server choke on a file I'd inadvertently saved as UTF-8 with BOM. That one took a while to figure out.

And just today, I was experimenting with character encoding. I changed my charset meta tag from UTF-8 to ISO-8859-1 and it completely killed all my ajax calls.

There seems to be no end to the ways I can screw up a file.

Dale



On Dec 10, 2009, at 9:35 PM, Tim 'Webko' Booth wrote:

> Of course, about 2 minutes after posting, I found the real culprit...
> 
>> Dear All,
>> 
>> I have been a given a server to play with. It does something very odd:
>> 
>> It will choke on a script if it has any sort of single line commenting, either // or #
>> 
>> It will run a script if you use the /* multi-line commenting */ format though.
>> 
>> Included files are not affected by this behaviour - even if they have a // comment in them, they perform as expected.
> 
> Somehow, an errant high ASCII character had crept into the two lines that I use on nearly every php page:
> 
> 	include_once('include/db_config.php');	// DataBase Configuration File.
> 	include_once('include/FX/FX.php');	// FX.php file
> 
> Just after the semi-colon - my other Mac servers didn't seem to care, but this Windows server sure does. Tested a bunch of other sites I've doen recently, and this set of code seems the only one affected - very strange, but at least explains why the behaviour went away when I changed it to multi-line commenting - able to use normal commetning again now...
> 
> Cheers
> 
> Webko
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list