Not exploding by PHP_EOL

[vlucas]

Not exploding by PHP_EOL

[vlucas]

I'm not sure. PHP_EOL should be your system's end of line character. I just did some research though and it seems like "\r\n" is best for wide compatability. Can you verify that explode("\r\n", ... ) works on your system?

[jtwebb]

"\r\n" doesn't work. It still doesn't break each line into a value. It just throws everything into $lines[0] (same as PHP_EOL). It's odd that it doesn't work since I have the same setup on a different local virtual server and deployment server and they both work fine. There's nothing different about this setup, yet it still won't work without using "\n".

[harm-less]

I've the same problem. I'm using IIS to simulate PHP and to parse the Dotenv class.
Apparently the PHP_EOL doesn't contain any line-break information, but explode("\n", ... ); does work on my system.

Update:
At a closer look, I think the PHP_EOL does contain a "\r\n", however, it of course doesn't fix the problem because only the "\n" here.

And I found a similar topic about this: avalanche123/doxphp#7

[QWp6t]

I don't think you should rely on PHP_EOL.

I would recommend using something like this: http://stackoverflow.com/questions/11066857/detect-eol-type-using-php

[harm-less]

It seems like PHP_EOL is a good practice when creating new lines dynamically, not when exploding.
http://stackoverflow.com/questions/4975411/when-do-i-use-php-eol-instead-of-n-and-vice-versa-ajax-jquery-client-problem

Perhaps you can use the first answer:
$lines = array_map("rtrim", explode("\n", $fc));
Or something similar since it will break on old macs. Perhaps something like this, I've tested this and it works fine at my system:
$lines = preg_split('/\r\n|\r|\n/', $fc);

[QWp6t]

This worked for me

ini_set("auto_detect_line_endings", true);
$lines = file($filePath);

It uses PHP's auto line detection (see: L852), which appears to be more or less the same as the last line of @harm-less's post.

I'd recommend going with his method on the off chance a user might not be happy with changing an ini setting (although you could use ini_get() and then change it back afterwards, but whatever; doesn't seem like that's necessary).

[vlucas]

This has been fixed.