> > Not sure I understand what the astAt/astINVOKE changes are about
> > (something to do with reporting an error at line XXX of file YYY.c?),
> > but won't these require a change in JNIAST?
>
> I can't immediately think of any. If astNOERR is left undefined, then the
> behaviour is unchanged from earlier versions - which is presumably what
> JNIAST wants. This new macro is to allow Tim to insert his own calls to
> astAt in his perl wrapper functions so that error messages issued by
> AST refer to the line number in the perl code rather than the C
> wrapper function.
Which makes debugging the Perl a whole lot easier...
> > Not sure how significant the new features are - since Peter is main
> > client of AST and the person who it's most effort for to effect the
> > rebuild, I'll let him decide whether we want to rebuild for V3.2-5.
The new features include log plots don't they? In which case both Peter
and I want this functionality on the Java side rather desparately for
SPLAT and FROG.
> Things are a bit fluid regarding AST at the moment. The work being done
> to produce perl wrapers is throwing up several (mostly minor) issues
> which will need fixing. So it may be best to wait until the rate at
> which bugs are discovered slows down a bit.
You'll be please to know that we've pretty much got it working now, along
with the PGPLOT and Perl/Tk graphics wrappers already mentioned Brad is
currently working on a PLPlot wrapper.
Al.
--
Dr. A. Allan, School of Physics, University of Exeter
|