[Nexus-developers] NXgetpath

[Peterson, Peter F.]

If you look at the python api, the second option is what was chosen.  
It actually has getpath (current name only path) and getlongpath (name  
and type separated by ':'). Then it takes both forms in openpath, the  
former searches for type, the latter uses the supplied type.

P^2

On Oct 27, 2009, at 11:17 AM, Mark Koennecke wrote:

> Hi,
>
> I looked at the implementation of NXgetpath in the C-API and as far  
> as I
> see it now, there are two options:
>
> - In principle the information required is there in the stacks of the
> underlying
>  physical file format driver code. Using this would require an  
> addition to
>  pNexusFunction and three specific implementations. Which is kind of  
> ugly.
> - The other option would be to implement this at the napi.c level.  
> And make
>  NXopen/closegroup, NXopen/closedata maintain a stack. On the plus  
> side of
>  this option is that only one implementation is required. The downside
> is that I
>  need to add yet another stack.
> I am tempted by the second solution. Has anyone opinions?
>
> Best Regards,
>
>    Mark
>
> _______________________________________________
> NeXus-developers mailing list
> NeXus-developers at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus-developers