Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI devel] RFC: Java MPI bindings
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2012-02-07 15:57:55

On Feb 7, 2012, at 3:33 PM, Paul H. Hargrove wrote:

> So I'd propose that the work be done on a branch and the RFC can be reissued when there is both
> a) a standard to which the bindings can claim to conform

I don't really agree with this statement; see my prior email.

> b) an implementation which has been shown to be stable

That's fair enough.

The implementation has zero performance impact on the rest of the code base (E.g., latency of C's MPI_Send). But the rest of the code stability does need to be proven, and definitely benefits from having others test it.

This is not an unusual pattern for the OMPI SVN trunk. People develop stuff on branches all the time and bring them in to the trunk. And sometimes it makes the trunk a little unstable for a while, despite the best of intentions and the best attempts at pre-testing before committing to the trunk (I know; I've been the cause of trunk instability before, too).

Case in point: some new MPI-3 functions were recently brought to the trunk. They had several mistakes in them that were not evident until others tried to compile / use them.

Jeff Squyres
For corporate legal information go to: