Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #29363 > unrolled thread

concatenation operator glyph

Back to article view | Back to comp.lang.java.programmer

Contents

  concatenation operator glyph Roedy Green <see_website@mindprod.com.invalid> - 2014-07-27 10:31 -0700
    Re: concatenation operator glyph Roedy Green <see_website@mindprod.com.invalid> - 2014-07-27 10:47 -0700
    Re: concatenation operator glyph Silvio <silvio@internet.com> - 2014-07-28 13:19 +0200
      Re: concatenation operator glyph Roedy Green <see_website@mindprod.com.invalid> - 2014-07-28 07:47 -0700
        Re: concatenation operator glyph Robert Klemme <shortcutter@googlemail.com> - 2014-07-28 18:11 +0200
        Re: concatenation operator glyph Silvio <silvio@internet.com> - 2014-07-28 19:01 +0200

#29363 — concatenation operator glyph

I have bugged the Unicode consortium to assign a code point for a
concatenation operator. If they say yes, the problem arises, what
should the corresponding glyph look like?

It should visually suggest joining.  I think should be left-right
symmetrical to reflect the symmetry of the operation. It should be
distinct from other symbols even at small font sizes.

This is a different problem from how to represent concatenation in
Java. It would be used in mathematical papers, documentation, and
perhaps published Java listings.


-- 
Roedy Green Canadian Mind Products http://mindprod.com
The art of strongly-typed language design is largely arranging 
that errors are automatically detected as soon as possible
in the compose, compile, run cycle.

[toc] | [next] | [standalone]

#29364

On Sun, 27 Jul 2014 10:31:58 -0700, Roedy Green
<see_website@mindprod.com.invalid> wrote, quoted or indirectly quoted
someone who said :

>It should visually suggest joining.  I think should be left-right
>symmetrical to reflect the symmetry of the operation. It should be
>distinct from other symbols even at small font sizes.

Mathematicians use two closely spaced vertical lines. Perhaps
something on that line that would not be confused with ||.
-- 
Roedy Green Canadian Mind Products http://mindprod.com
The art of strongly-typed language design is largely arranging 
that errors are automatically detected as soon as possible
in the compose, compile, run cycle.

[toc] | [prev] | [next] | [standalone]

#29386

On 07/27/2014 07:31 PM, Roedy Green wrote:
> I have bugged the Unicode consortium to assign a code point for a
> concatenation operator. If they say yes, the problem arises, what
> should the corresponding glyph look like?
>
> It should visually suggest joining.  I think should be left-right
> symmetrical to reflect the symmetry of the operation. It should be
> distinct from other symbols even at small font sizes.
>
> This is a different problem from how to represent concatenation in
> Java. It would be used in mathematical papers, documentation, and
> perhaps published Java listings.
>
>

Please stop pushing the concatenation topic. It is a non issue and you 
are taking it way too far. It is not an actual problem and if there is a 
problem it is not that + concatenates strings (as it does for lists and 
sequences in other languages) but that Java implicitly converts anything 
to String when used in combination with a String and the + operator. 
That, if you will, is a Java blunder.

[toc] | [prev] | [next] | [standalone]

#29394

On Mon, 28 Jul 2014 13:19:00 +0200, Silvio <silvio@internet.com>
wrote, quoted or indirectly quoted someone who said :


>Please stop pushing the concatenation topic. It is a non issue and you 
>are taking it way too far.

What percentage of your programs contain an concatenation operator?

Nearly all of mine do.
-- 
Roedy Green Canadian Mind Products http://mindprod.com
The art of strongly-typed language design is largely arranging 
that errors are automatically detected as soon as possible
in the compose, compile, run cycle.

[toc] | [prev] | [next] | [standalone]

#29396

On 28.07.2014 16:47, Roedy Green wrote:
> On Mon, 28 Jul 2014 13:19:00 +0200, Silvio <silvio@internet.com>
> wrote, quoted or indirectly quoted someone who said :
>
>
>> Please stop pushing the concatenation topic. It is a non issue and you
>> are taking it way too far.
>
> What percentage of your programs contain an concatenation operator?

What does this have to do with the topic?  And why do you bring up the 
topic of a concatenation operator code point for Unicode in a Java 
forum, where you explicitly state that "This is a different problem from 
how to represent concatenation in Java."?  Something seems to be eluding me.

> Nearly all of mine do.

There's also StringBuilder which is usually more efficient when Strings 
are created with loops.

Kind regards

	robert

[toc] | [prev] | [next] | [standalone]

#29399

On 07/28/2014 04:47 PM, Roedy Green wrote:
> On Mon, 28 Jul 2014 13:19:00 +0200, Silvio <silvio@internet.com>
> wrote, quoted or indirectly quoted someone who said :
>
>
>> Please stop pushing the concatenation topic. It is a non issue and you
>> are taking it way too far.
>
> What percentage of your programs contain an concatenation operator?
>
> Nearly all of mine do.
>

Probably most of mine do as well, although only in few specific and 
encapsulated locations. Programs with string manipulation scattered all 
over the place are either tryout toys or they belong in the garbage bin.

It does not make String concatenation a special or even moderately 
important topic in any way. Most of my programs do IO. I do a lot of XML 
processing as well, quite some database access, HTTP etc. I would oppose 
introducing (or overloading) operators for that as well. And these are 
what I do consider major topics.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.java.programmer

csiph-web