[Nexus-developers] SWIG NeXus interface

Mark Koennecke Mark.Koennecke at psi.ch
Tue Dec 17 13:38:33 GMT 2002


  High, back to this SWIG business again, 

On Wed, 27 Nov 2002, Jens [iso-8859-1] Krüger wrote:

> Hi Mark,  hi Ray,
> 
> Am Donnerstag, 21. November 2002 08:27 schrieb Mark Koennecke:
> > Dear Ray,
> >
> > On Wed, 20 Nov 2002, Ray Osborn wrote:
> > > On 2002/11/20 7:37, "Mark Koennecke" <Mark.Koennecke at psi.ch> wrote:
> > >
> 
> I think, after tagging the current release of the distribution and creating a 
> branch for bug-fixes for the this release it should be no problem to add the 
> SWIG support into the CVS in the development trunk (the same as the main 
> trunk). If there is something wrong or worse you may fix  or remove it. It 
> would be better to test it from the CVS than create an extra tar.gz or patch 
> and you have to add it to the distribution. 
> 
  I see a good reason for tagging the current status as 2.0, so that we
  can get back to it if we need to. I do not see the point in creating
  a branch though. The procedure we used so far was that the accumulated
  bug fixes and additions gave rise to the next version. What do I gain 
  with the extra administrative overhead of a branch? IMHO, a branch would
  only be needed if we run a fix against the old 1.3.x version.  

> > > Hi Mark,
> > > I think that it would be helpful for the other developers to try it out
> > > before we release it to the public.  I played around with SWIG, and soon
> > > realized that it raises a number of issues, e.g., Python seemed to
> > > require the NXhandle pointer to be initialized as a null pointer before
> > > the first call to NXopen.  I don't know if you have solved all those
> > > problems, but I would like to see what you've done and then discuss how
> > > the user will want
> >

   Let's sort this, I want to put the SWIG stuff into the repository
   before Xmas. Also we have some important bug fixes as well.

                    Regards,

			Mark Koennecke







More information about the NeXus-developers mailing list