Re: PHP 4.0.5 Parse Problems

In article <c5e3392dba1416355674b7187be1ece0@news.php.net>, ben@jatosoft.com (Ben Gollmer) wrote: > >I only mention them since they got parsed before. They are php files > >that the designers here have created in HomeSite and saved as PC > >format, so they are basically 1 long line when I open them in vi, and > >have ^M's everywhere. If they pull them back into HomeSite and save > >as UNIX format and upload, no problem. What changed in PHP that would > >make this difference. I would just tell them to do this with all the > >problem ones, but there are a lot. > >This is on OpenBSD, btw. Thanks. > >-Ken > > I tried changing the line endings of some of my files, but to no avail. > The only thing that seems to work for me is to create a new file using > vi or pico - PHP then parses it perfectly. For now, PHP 4.0.5 isn't a What transfer mode is your FTP client using to transfer the files? I forget whether it's binary or ASCII mode (I *think the latter...) that automatically adjusts linebreak/newline characters for you, but you might want to try toggling the client's setting to see if those "changed" line endings can be made to stay "changed" after transfer. (BTW, text editors often have an option allowing the user to specify which OS's linebreak style to use when saving. Sounds like 4.0.5. may be requiring more of us to take advantage of this type of feature.) -- CC