Re: [agtk-devel] AG API -- list return type

[Kazuaki M. <ma...@un...>]

Hello everyone,

Thanks for the discussion.

Matthias Thomae wrote:

>  > The new types would be something like the following.  These will be
>  > lists (or arrays) in C++, Python, Java and Tcl.
> 
> Does that mean, if I now process the data as list in Tcl, I don't have
> to make any changes?

With the current API, I think you'd convert the return values of the
affected functions to lists by, perhaps, using "split".

set annSet [split [::AG::GetAnnotationSetByOffset $AGID 0.100]]

This would need to be changed to something like the following when the new
API comes out.

set annSet [::AG::GetAnnotationSetByOffset $AGID 0.100]

Things required in the change are perhaps simply 1) grep'ing the affected
functions in the code, and 2) removing a few things from the code.

Steve Cassidy wrote:

> The compile time switch might be a good way to manage the change 
> but in the end everyone will be sure to move over given the obvious 
> need for this.

Mark Liberman wrote:

> Another way to manage the change would be to re-name the functions
> (e.g. "GetAnnotationSetByOffset" -> "GetAnnotationListByOffset")
> and deprecate the old ones.

I think both are good ideas.  Are there any opinions as to which of these
is better?  Perhaps, we can choose one of these two methods, and release
the new API as version 1.2 or 2.0 quite soon.

Thank you,
- Kazuaki Maeda (LDC)