[Nexus-developers] NeXus linking, Java

[Peterson, Peter F.]

Mark,

I like the idea of having renamed links. I've abandoned HDF4 myself so
if it means copying data to get the same effect it doesn't *directly*
bother me. I assume that you will still keep the target attributes as
they are supposed to be. And adding an API function is the appropriate
way to do this. It should probably confirm that the renamed link does
have a different name, otherwise generate a traditional link.

About the java stuff: Would it be appropriate to keep the old stuff
where it is, but add @deprecated tags to everything? Then changes are
only made to the new stuff with the different package name. While you
are reworking the java, are you also incorporating the code I gave you
to make it feel more like Java?

P^2

-----Original Message-----
From: nexus-developers-bounces at nexusformat.org
[mailto:nexus-developers-bounces at nexusformat.org] On Behalf Of Mark
Koennecke
Sent: Friday, December 15, 2006 6:23 AM
To: nexus-developers at nexusformat.org
Subject: [Nexus-developers] NeXus linking, Java

High,

As promised I looked into the issue of linking items with a different 
name in NeXus. The results:
- Works in HDF-5
- Works - XML
- Does NOT work in HDF-4. In HDF-4 a group is implemented as a list of 
reference ID's and the name is
 an attribute of the object itself. In HDF-4 a renamed link can only be 
implemented by copying the data.

Do we want this, with a new API call:
       NXmakenamedlink(NXhandle h, NXlink target, char *newname);
?

For the Java-API I now repackaged the stuff from neutron.nexus to 
org.nexusformat. It works, at least the
test program works. But I am still worried because this might break 
existing code. So I want some encouragement
to commit this.

              Best Regards,

                          Mark
 

_______________________________________________
NeXus-developers mailing list
NeXus-developers at nexusformat.org
http://lists.nexusformat.org/mailman/listinfo/nexus-developers