#15211 [Opn->Bgs]: println?
| From: | iliaa@php.net | Date: | Fri, 07 Feb 2003 03:08:28 +0000 |
| Subject: | #15211 [Opn->Bgs]: println? | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-32349@lists.php.net to get a copy of this message | ||
ID: 15211
Updated by: iliaa@php.net
Reported By: dark_panda@hushmail.com
-Status: Open
+Status: Bogus
Bug Type: Feature/Change Request
PHP Version: 4.1.1
New Comment:
Sorry, but your problem does not imply a bug in PHP itself. For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system
is not the
appropriate forum for asking support questions.
Thank you for your interest in PHP.
Given the number of print functions already in PHP this seem pointless,
especially considering it'd only print a single character.
Previous Comments:
------------------------------------------------------------------------
[2002-06-08 10:38:26] bigredlinux@yahoo.com
Actually, what would be HUGE is if println could determine the sapi
module it is running as and then add the endline appropriately, meaning
for the web it would add a '<br clear="all" />' tag after the line.
But honestly, if php is really going to be considered for commandline
scripting, it needs a println() feature.
------------------------------------------------------------------------
[2002-01-24 13:36:56] dark_panda@hushmail.com
I'm in the midst of doing quite a bit of shell/command line
stuff with PHP, and I think it would be kind of useful to
have a println construct, much like in Java or a number of
other languages. println is identical to print, but a
newline/carriage return is appended to the output.
I know I could just write function in PHP or even a
function in an extension to provide the same functionality,
but it might as well be in the language itself, if only
because it may be used often enough to warrant inclusion.
(I know I'd use it all the time.)
I started trying to add it myself (I can see that it would
go in the Zend engine, correct?) but after reminding myself
that I've never used Lex before (nor really looked at the
Zend code) I decided that this would be best left to
someone who actually knows what they're doing when it
comes to the Zend engine.
The only problem I can think of is portability,
specifically the oft-cursed differences between OS newline
sequences. (Is it \n? \r\n? \n\r? Dammit?!) Doesn't seem
like a huge issue, though, does it?
J
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=15211&edit=1