X-Received: by 10.66.86.166 with SMTP id q6mr1649879paz.44.1355987741561; Wed, 19 Dec 2012 23:15:41 -0800 (PST)
Received: by 10.50.219.133 with SMTP id po5mr1273054igc.17.1355987741494; Wed, 19 Dec 2012 23:15:41 -0800 (PST)
Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!f6no3738934pbd.1!news-out.google.com!6ni51708pbd.1!nntp.google.com!f6no3738932pbd.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.java.programmer
Date: Wed, 19 Dec 2012 23:15:41 -0800 (PST)
In-Reply-To: <50d27cf0$0$294$14726298@news.sunsite.dk>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=173.164.137.214; posting-account=CP-lKQoAAAAGtB5diOuGlDQk0jIwmH0T
NNTP-Posting-Host: 173.164.137.214
References: <7f36342c-2331-4484-874b-4a0f8953f160@googlegroups.com> <ka6lj0$mgp$1@news2.ipartners.pl> <ka88nr$128$1@dont-email.me> <kabtes$76d$1@news2.ipartners.pl> <Uaiys.16310$sm1.15526@newsfe22.iad> <kaehb9$1fmn$1@news2.ipartners.pl> <lICys.64314$2v.59843@newsfe05.iad> <kaf0ak$1mrb$1@news2.ipartners.pl> <M1Lys.8038$fh5.476@newsfe26.iad> <kafvoc$jjp$1@dont-email.me> <b1Pzs.16498$Id.11979@newsfe24.iad> <1rfmfoqs8bzc6.4pavkn8829dk$.dlg@40tude.net> <kaogn8$jkm$1@dont-email.me> <qdrd1mgseyq1$.1upmnl6v646ec$.dlg@40tude.net> <vEXzs.27998$tG.2948@newsfe15.iad> <50d25c08$0$282$14726298@news.sunsite.dk> <ybtAs.23610$411.13683@newsfe02.iad> <50d27cf0$0$294$14726298@news.sunsite.dk>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <d174faaf-a65f-4fa6-8ebb-338e5c9ea753@googlegroups.com>
Subject: Re: multi-line Strings
From: Lew <lewbloch@gmail.com>
Injection-Date: Thu, 20 Dec 2012 07:15:41 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Xref: csiph.com comp.lang.java.programmer:20617

Arne Vajh=F8j wrote:
> The extended name should be related to the purpose not the factor

This is best practice, and more consistently followed in proportion to expe=
rience in=20
the field, I assess.

> to handle the case where a rounding is changed for some calculations.
>=20
> FACTOR_TO_ROUND_DOLLAR_AMOUNT
> FACTOR_TO_ROUND_DISTANCE_MEASUREMENT
> etc.

These names serve your pedagogical purpose, but simultaneously serve to=20
illustrate that there's an element of style involved, not just engineering.

To my eye those names are longer than need be. I cannot and will not claim =
any=20
objective validity to that assessment, but I would in a project push for mo=
re elegant=20
names.

I don't necessarily mean abbreviated. Elegance is an ineffable match of for=
m to=20
function to aesthetic expression. Sometimes terse, sometimes verbose, elega=
nce=20
adapts to the circumstance and objectives of the moment.

My preference in this instance for the proffered scenarios would be more li=
ke

DOLLAR_ROUNDER
DISTANCE_ROUNDER

My reasoning involves degree of information conveyed relative to length and=
 subitizability
of morpheme count.

But my action is based on a more intuitive sense, arguably one that subsume=
s the=20
rationalized basis.

--=20
Lew