On 2012-01-16 11:37- Andrew Ross wrote:
> Alan,
>
> Many thanks for this! I've been slightly worried about this for some time
> so it's nice that you've found a neater solution.
>
> Your documentation changes missed out a tag though which caused octave
> documentation builds to fail. I've fixe
On Sat, Jan 14, 2012 at 04:04:52PM -0800, Alan Irwin wrote:
> On 2012-01-12 21:39-0800 Alan W. Irwin wrote:
>
> > However, I will change my mind if that swig idiosyncrasy ever
> > disappears so swig just deploys code fragments in the wrapper code in
> > the exact order of the argument list. In th
On 2012-01-12 21:39-0800 Alan W. Irwin wrote:
> However, I will change my mind if that swig idiosyncrasy ever
> disappears so swig just deploys code fragments in the wrapper code in
> the exact order of the argument list. In that case, Xlen and Ylen
> will be available from prior NumPy 1-D arrays
I have been discussing this topic off-list with Andrew, but I thought
my conclusions should be on-list in case this topic ever comes up
again.
What started this topic is I implemented a Python interface to ephcom
(part of the Time Ephemerides project) following what is done for the
array typemaps
