PHP已经知道当前系统的换行符。只用EOL常数。

explode(PHP_EOL,$string)

你不需要preg_*函数、preg模式、str_replace within等，就可以通过换行成功地将字符串分解为数组。在所有场景中，无论是Linux、Mac还是Windows，这都可以。

<?php
    $array = explode(PHP_EOL, $string);
    // ...
    $string = implode(PHP_EOL, $array);
?>

PHP_EOL是一个常量，保存服务器平台使用的换行符。

PHP已经知道当前系统的换行符。只用EOL常数。

explode(PHP_EOL,$string)

这个页面上有很多直接或间接的答案，评论中也有一些很好的建议，但没有一个答案能代表我在自己的项目中所写的内容。

PHP转义序列\R文档:https://www.php.net/manual/en/regexp.reference.escape.php#:~:text=line%20break，\ R \n

代码:(演示)

$string = '
My text1

My text2


My text3


';

var_export(
    preg_split('/\R+/', $string, 0, PREG_SPLIT_NO_EMPTY)
);

输出:

array (
  0 => 'My text1',
  1 => 'My text2',
  2 => 'My text3',
)

OP没有提到从行中删除水平空白字符，因此不期望在变量(系统不可知)新行上爆炸时删除\s或\h。

虽然PHP_EOL是明智的建议，但当换行序列来自另一个操作系统时，它缺乏适当地爆炸字符串的灵活性。

使用非正则表达式爆炸往往不太直接，因为它需要字符串准备。此外，如果有多余的空白线需要清除，爆炸后可能会有清理工作。

Using \R+ (one or more consecutive newline sequences) and the PREG_SPLIT_NO_EMPTY function flag will deliver a gap-less, indexed array in a single, concise function call. Some people have a bias against regular expressions, but this is a perfect case for why regex should be used. If performance is a concern for valid reasons (e.g. you are processing hundreds of thousands of points of data), then go ahead and invest in benchmarking and micro-optimization. Beyond that, just use this one-line of code so that your code is brief, robust, and direct.

这个方法对我来说总是有效的:

$uniquepattern = "gd$#%@&~#" // Any set of characters which you don’t expect to be present in user input $_POST['text']. Better use at least 32 characters.
$textarray = explode($uniquepattern, str_replace("\r", "", str_replace("\n", $uniquepattern, $_POST['text'])));

我在PHP文档中找到了这个:

<?php
  // Split the phrase by any number of commas or space characters,
  // which include " ", \r, \t, \n and \f

  $keywords = preg_split("/[\s,]+/", "hypertext language, programming");
  print_r($keywords);
?>