| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

Last 100 entries

Chat Wars; Real-life Financial Co Without ACID Database...; Flexible Muscle-Based Locomotion for Bipedal Creatures; SQL Performance Explained; The Little Manual of API Design; Multiple Word Sizes; CRC - Next Steps; FizzBuzz; Update on CRCs; Decent Links / Discussion Community; Automated Reasoning About LLVM Optimizations and Undefined Behavior; A Painless Guide To CRC Error Detection Algorithms; Tests in Julia; Dave Eggers: what's so funny about peace, love and Starship?; Cello - High Level C Programming; autoreconf needs tar; Will Self Goes To Heathrow; Top 5 BioInformatics Papers; Vasovagal Response; Good Food in Vina; Chilean Drug Criminals Use Subsitution Cipher; Adrenaline; Stiglitz on the Impact of Technology; Why Not; How I Am 5; Lenovo X240 OpenSuse 13.1; NSA and GCHQ - Psychological Trolls; Finite Fields in Julia (Defining Your Own Number Type); Julian Assange; Starting Qemu on OpenSuse; Noisy GAs/TMs; Venezuela; Reinstalling GRUB with EFI; Instructions For Disabling KDE Indexing; Evolving Speakers; Changing Salt Size in Simple Crypt 3.0.0; Logarithmic Map (Moved); More Info; Words Found in Voynich Manuscript; An Inventory Of 3D Space-Filling Curves; Foxes Using Magnetic Fields To Hunt; 5 Rounds RC5 No Rotation; JP Morgan and Madoff; Ori - Secure, Distributed File System; Physical Unclonable Functions (PUFs); Prejudice on Reddit; Recursion OK; Optimizing Julia Code; Cash Handouts in Brazil; Couple Nice Music Videos; It Also Works!; Adaptive Plaintext; It Works!; RC5 Without Rotation (2); 8 Years...; Attack Against Encrypted Linux Disks; Pushing Back On NSA At IETF; Summary of Experimental Ethics; Very Good Talk On Security, Snowden; Locusts are Grasshoppers!; Vagrant (OpenSuse and IDEs); Interesting Take On Mandela's Context; Haskell Cabal O(n^2) / O(n) Fix; How I Am 4; Chilean Charity Supporting Women; Doing SSH right; Festival of Urban Intervention; Neat Idea - Wormholes Provide Entanglement; And a Link....; Simple Encryption for Python 2.7; OpenSuse 13.1 Is Better!; Little Gain...; More Details on Technofull Damage; Palmrest Cracked Too....; Tecnofull (Lenovo Support) Is Fucking Useless; The Neuroscientist Who Discovered He Was a Psychopath; Interpolating Polynomials; Bottlehead Crack as Pre-amp; Ooops K702!; Bottlehead Crack, AKG K701; Breaking RC5 Without Rotation; Great post thank you; Big Balls of Mud; Phabricator - Tools for working together; Amazing Julia RC5 Code Parameterized By Word Size; Chi-Square Can Be Two-Sided; Why Do Brits Accept Surveillance?; Statistics Done Wrong; Mesas Trape from Bravo; European Report on Crypto Primitives and Protocols; Interesting Omissions; Oryx And Crake (Margaret Atwood); Music and Theory; My Arduino Programs; Elliptic Curve Crypto; Re: Licensing Interpreted Code; Licensing Interpreted Code; ASUS 1015E-DS03 OpenSuse 12.3 SSD; translating lettuce feature files into stub steps files; Re: translating lettuce feature files into stub steps files; A Tale of Two Psychiatrists

© 2006-2013 Andrew Cooke (site) / post authors (content).

Using a New Scope to Avoid Type Capture with Java Generics

From: "andrew cooke" <andrew@...>

Date: Tue, 9 Sep 2008 08:25:18 -0400 (CLT)

This is a little trick for Java Generics that's worth knowing.  It's
mentioned very briefly in Wadler's book (p27-8), but you could easily miss
it.

The problem happens when you are dealing with type parameters that you
know are consistent, but which are not explicit in your code.  This is
common if you are processing a not-completely-typed collection.

To make things clearer, I'll use the following example:  Consider a system
that transfers various values from one place to another (perhaps it is a
scheduler sending messages of different types within a system).

We might have an interface that can both provide and receive certain
message types:

public interface Connection<Type>
{
  Type read();
  void write(Type value);
}

And our scheduler might look something like this:

class Scheduler
{
  public void process(Collection<Connection<?>> cnxs)
  {
    for (Connection<?> cns: cnxs) {
      cnx.write(cnx.read);
    }
  }
}

(Note that <?> is shorthand for <? extends Object> and we use it here
because the cnxs collection contains a Connections with a variety of
different type parameters).

Unfortunately that won't compile!  The error given be Eclipse with Java
1.6 is "The method write(capture#2-of ?) in the type
Connection<capture#2-of ?> is not applicable for the arguments
(capture#3-of ?)".

The reason this won't compile is that the type parameter for the value
being returned by the Connection and the type parameter for the value it
will receive are being treated separately.  Each is being treated as
"capture-of ?" which means "some subclass of Object".  And the compiler is
then (understandably) saying "I can't send 'subclass X of Object' to a
method that expects 'subclass Y of Object' because I don't know if they
are the same subclass".

To make this work we need to introduce the common type parameter
explicitly.  Unfortunately the following code, or something like it,
doesn't work (as far as I can tell).  There is no way to introduce a type
parameter in the middle of a block of code (what we really want here is
better support for polymorphism):

class Scheduler
{
  public void process(Collection<Connection<?>> cnxs)
  {
    // syntax error!
    for (<E> Connection<E> cns: cnxs) {
      E value = cnx.read();
      cnx.write(value);
    }
  }
}

But what we can do is add a helper method that introduces a new type
parameter:

class Scheduler
{
  public void process(Collection<Connection<?>> cnxs)
  {
    for (Connection<?> cnx: cnxs) {
      helper(cnx);
    }
  }
  private <E> void helper(Connection<E> cnx)
  {
    E value = cnx.read();
    cnx.write(value);
  }
}

This does what we want!  The code validates, compiles, and runs.

In summary then:  Sometimes you can "lose" an explicit generic type
parameter (often because you are dealing with a collection of different
types).  You can re-introduce that type parameter by adding an extra
helper method.

Andrew

Comment on this post