Req #12428 [Com]: I want 'echoln'

[php at guerrillamailblock dot com]

Edit report at http://bugs.php.net/bug.php?id=12428&edit=1

 ID:   12428
 Comment by:       php at guerrillamailblock dot com
 Reported by:  rvtol at xs4all dot nl
 Summary:  I want 'echoln'
 Status:   Closed
 Type: Feature/Change Request
 Package:  Feature/Change Request
 Operating System: any
 PHP Version:  4.0.6

 New Comment:

Why not?


Previous Comments:

[2002-04-27 15:50:40] j...@php.net

not going to happen.


[2001-07-27 11:04:33] rvtol at xs4all dot nl

Is there something like an 'echoln'? 



I use echo $var,'\n' quite often, 

so an 'echoln' would be very handy. 



Or even better would be macros:



#define echoln echo $, 'n'



Thanks, Ruud







-- 
Edit this bug report at http://bugs.php.net/bug.php?id=12428&edit=1

Req #51440 [Com]: request extend echo print sentences

[php at guerrillamailblock dot com]

Edit report at http://bugs.php.net/bug.php?id=51440&edit=1

 ID:   51440
 Comment by:       php at guerrillamailblock dot com
 Reported by:  datamine dot maramirezc at gmail dot com
 Summary:  request extend echo print sentences
 Status:   Wont fix
 Type: Feature/Change Request
 Package:  Output Control
 Operating System: any
 PHP Version:  Irrelevant

 New Comment:

No, this is not Pascal, this is PHP. So what?


Previous Comments:

[2010-03-30 21:41:08] f...@php.net

This is not Pascal.


[2010-03-30 19:55:31] datamine dot maramirezc at gmail dot com

Description:

This is a request. 

Please, add println and echoln sentences.



Instead of writing this several times:





print "whatever\n";

echo "whatever\n";





We could use a more compact:





println "whatever";

echoln "whatever";







It's useful when the program outputs a single string for a H.T.M.L.
single line.

This way, it's easier to debug the H.T.M.L. code generated.



Thanks.









-- 
Edit this bug report at http://bugs.php.net/bug.php?id=51440&edit=1

Req #15211 [Com]: println?

[php at guerrillamailblock dot com]

Edit report at http://bugs.php.net/bug.php?id=15211&edit=1

 ID:  15211
 Comment by:  php at guerrillamailblock dot com
 Reported by: dark_panda at hushmail dot com
 Summary: println?
 Status:  Bogus
 Type:Feature/Change Request
 Package: Feature/Change Request
 PHP Version: 4.1.1

 New Comment:

ugly:

echo "hello world\n";# bad practice to use double quotes
everywhere

echo 'hello world', "\n";# why do I have to write >>, "\n"<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.


[2002-06-08 10:38:26] bigredlinux at yahoo dot 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 '' 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 at hushmail dot 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/bug.php?id=15211&edit=1