Java Puzzler, double chars

By

A teaser which uses char and double

The following compiles and produces an output. Can you explain why? 

char ch = 'A';
ch *= 1.5;
System.out.println(ch); // prints 'a'

Here is a hint for a simpler example. 

byte b = 100;
b /= 2.5;
System.out.println(b); // prints 40

Comments

  1. Aleksandr3 January 2012 at 11:34

    Well... Duh!
    'A' is 65.
    'a' is 97

    65 * 1.5 = 97.5

    And since char is an integer...

    ReplyDelete
  2. Vladimir Dolzhenko3 January 2012 at 11:48

    @Aleksandr

    char isn't an integer - it's unsigned integer

    ReplyDelete
  3. Peter Lawrey3 January 2012 at 11:52

    Or being pedantic, char is an unsigned short. ;)

    ReplyDelete
  4. Vladimir Dolzhenko3 January 2012 at 12:49

    That's another java puzzler.

    JLS the 3rd edition:
    The Unicode standard was originally designed as a fixed-width 16-bit character encoding. It has since been changed to allow for characters whose representation requires more than 16 bits. The range of legal code points is now U+0000 to U+10FFFF, using the hexadecimal U+n notation.

    So, it is not a 32-bit integer, in the same time it definitely more than short.

    ReplyDelete
  5. Peter Lawrey3 January 2012 at 13:12

    @Vladimir The String and Character classes now support "code points" which assume a String is UTF-16 encoded for characters. http://en.wikipedia.org/wiki/UTF-16

    In the case of Character there are pairs of methods.

    public static boolean isLowerCase(char ch)

    public static boolean isLowerCase(int codePoint)

    http://docs.oracle.com/javase/7/docs/api/java/lang/Character.html


    Character.MAX_VALUE is still 65535, and char is still 16-bit, but code points use int values though as you point out, not the full range of 32-bit values. ;)

    ReplyDelete

Post a Comment

Popular posts from this blog

Java is Very Fast, If You Don’t Create Many Objects

By
Image
  You still have to watch how many objects you create. This article looks at a benchmark passing events over TCP/IP at 4 billion events per minute using the net.openhft.chronicle.wire.channel package in Chronicle Wire and why we still avoid object allocations..  One of the key optimisations is creating almost no garbage. Allocation is a very cheap operation and collection of very short-lived objects is also very cheap. Does this really make a difference? What difference does one small object per event (44 bytes) make to the performance in a throughput test where GC pauses are amortised? While allocation is as efficient as possible, it doesn’t avoid the memory pressure on the L1/L2 caches of your CPUs and when many cores are busy, they are contending for memory in the shared L3 cache.  Results Benchmark on a Ryzen 5950X with Ubuntu 22.10. JVM Vendor, Version No objects Throughput, Average Latency* One object per event Throughput, Average Latency* Azul Zulu 1.8.0_322 60.6 M event/s, 528
Read more

System wide unique nanosecond timestamps

By
A Unique Identifier can be very useful for tracing. Those ids are even more useful when they contain a high-resolution timestamp.  Not only do they record the time of an event, but if unique can help trace events as they pass through the system. Such unique timestamps however can be expensive depending on how they are implemented.   This post explores a lightweight means of producing a unique, monotonically increasing system-wide nano-second resolution timestamp available in our open-source library. Uses for Unique Identifiers Unique identifiers can be useful to associate with a piece of information so that information can be referred to later unambiguously. This could be an event, a request, an order id, or a customer id. They can naturally be used as a primary key in a database or key/value store to retrieve that information later. One of the challenges of generating these identifiers is avoiding creating duplicates while not having an increasing cost.  You could record every identi
Read more

Comparing Approaches to Durability in Low Latency Messaging Queues

By
Image
  A significant feature of Chronicle Queue Enterprise is support for TCP replication across multiple servers to ensure the high availability of application infrastructure. I generally believe that replicating data to a secondary system is faster than syncing to disk, assuming the round trip network delay wasn’t high due to quality networks and co-located redundant servers. This is the first time I have benchmarked it with a realistic example. Little’s Law and Why Latency Matters In many cases, the assumption is that the latency won't be a problem as long as throughput is high enough. However, latency is often a key factor in why the throughput isn’t high enough. Little’s law states, “ the long-term average number  L  of customers in a  stationary  system is equal to the long-term average effective arrival rate  λ  multiplied by the average time  W  that a customer spends in the system”. In computer terminology, the level of concurrency or parallelism a system has to support must be
Read more