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.

C-ORM: docs, API.

Last 100 entries

[Link] Linux Threads; [Link] Punycode; [Link] Bull / Girl Statues on Wall Street; [Link] Beautiful Chair Video; Update: Lower Pressures; [Link] Neat Python Exceptions; [Link] Fix for Windows 10 to Avoid Ads; [Link] Attacks on ZRTP; [Link] UK Jazz Invasion; [Review] Cuba; [Link] Aricle on Gender Reversal of US Presidential Debate; {OpenSuse] Fix for Network Offline in Updater Applet; [Link] Parkinson's Related to Gut Flora; Farellones Bike Park; [Meta] Tags; Update: Second Ride; Schwalbe Thunder Burt 2.1 v Continental X-King 2.4; Mountain Biking in Santiago; Books on Ethics; Security Fail from Command Driven Interface; Everything Old is New Again; Interesting Take on Trump's Lies; Chutney v6; References on Entropy; Amusing "Alexa.." broadcast; The Shame of Chile's Education System; Playing mp4 gifs in Firefox on Opensuses Leap 42.2; Concurrency at Microsoft; Globalisation: Uk -> Chile; OpenSuse 42.2 and Synaptics Touch-Pads; Even; Cherry Jam; Lebanese Writer Amin Maalouf; C++ - it's the language of the future; Learning From Trump; Chinese Writer Hu Fayun; And; Apricot Jam; Also; Excellent Article on USA Politics; Oh Metafilter; Prejudice Against The Rurals; Also, Zizek; Trump; Why Trump Won; Doxygen + Latex on CentOS 6; SMASH - Solve 5 Biggest Problems in Physics; Good article on racism, brexit, and social divides; Grandaddy are back!; Consciousness From Max Entropy; Democrats; Harvard Will Fix Black Poverty; Modelling Bicycle Wheels; Amusing Polling Outlier; If Labour keeps telling working class people...; Populism and Choice; Books on Defeat; Enrique Ferrari - Argentine Author; Transcript of German Scientists on Learning of Hiroshima; Calvert Journal; Owen Jones on Twitter; Possible Japanese Authors; Complex American Literature; Chutney v5; Weird Componentized Virus; Interesting Argentinian Author - Antonio Di Benedetto; Useful Thread on MetaPhysics; RAND on fighting online anarchy (2001); NSA Hacked; Very Good LRB Article on Brexit; Nussbaum on Anger; Tasting; Apple + Kiwi Jam; Hit Me; Sudoku - CSP + Chaos; Recycling Electronics In Santiago; Vector Displays in OpenGL; And Anti-Aliased; OpenGL - Render via Intermediate Texture; And Garmin Connect; Using Garmin Forerunner 230 With Linux; (Beating Dead Horse) StackOverflow; Current State of Justice in China; Axiom of Determinacy; Ewww; Fee Chaos Book; Course on Differential Geometry; Okay, but...; Sparse Matrices, Deep Learning; Sounds Bad; Applebaum Rape; Tomato Chutney v4; Have to add...; Culturally Liberal and Nothing More; Weird Finite / Infinite Result; Your diamond is a beaten up mess; Maths Books; Good Bike Route from Providencia / Las Condes to Panul; Iain Pears (Author of Complex Plots); Plum Jam; Excellent

© 2006-2017 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