Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 May 2020 15:44:18 -0500
From:      Tim Daneliuk <tundra@tundraware.com>
To:        FreeBSD Mailing List <freebsd-questions@freebsd.org>
Subject:   Re: Multi-line text output via printf() et al.
Message-ID:  <c9d3f4cd-a405-c404-8f82-cf2de5a0c9db@tundraware.com>
In-Reply-To: <20200514220904.7a4c1e28.freebsd@edvax.de>
References:  <20200514220904.7a4c1e28.freebsd@edvax.de>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 5/14/20 3:09 PM, Polytropon wrote:
> What is the _proper_ way of printing multiple lines?
> 
> My research basically did bring up the following methods:

<Threadjack>

Warning - Pet Peeve follows, ignore me if you think it's stupid ...

However you decide to do it, can we _please_ stop embedding literal strings
in printf(), python print(), and so forth?  Strings should be pulled out
as variables into one centrally maintained location in the code.  Why?
Because, someday, you may actually want to have your code run with output
in something other than your native language.  Because strings are often
reused in several places in the code.  Because you may someday actually
want to use unicode characters.

You haven't lived until you've had to scour thousands of lines of code
looking for literal strings or having those strings embedded symbolically,
deep down in the guts of the code.

If factoring code is a good practice, so too is factoring string literals.

</Threadjack>

-- 
----------------------------------------------------------------------------
Tim Daneliuk     tundra@tundraware.com
PGP Key:         http://www.tundraware.com/PGP/




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?c9d3f4cd-a405-c404-8f82-cf2de5a0c9db>