Thanks to a patch supplied by Tristan Carel there is a fixed version of
UseSWIG.cmake that I have (temporarily until this fix gets into an official
CMake version) made part of our PLplot build system. This version of
UseSWIG.cmake and the build system changes to use this modified module are
availa
Andrew Ross wrote:
>Ah yes. I should have looked more closely at this. Was there a reason
>you didn't do this for the plvect / plcont functions in the F95
>bindings? I'm not sure I would advocate changing this now as we already
>have plvect / plcont implemented, although with different arguments t
On Wed, Dec 12, 2007 at 09:51:59AM +0100, Arjen Markus wrote:
> Andrew Ross wrote:
>
> >>Hello Andrew,
> >>
> >>is that the reason for plvec2? Because Fortran, ever since it supported
> >>user-defined
> >>functions, so at least from FORTRAN IV onwards, has supported passing
> >>function names as
Andrew Ross wrote:
On Wed, Dec 12, 2007 at 09:20:46AM +0100, Arjen Markus wrote:
Andrew Ross wrote:
plvec2 is equivalent to calling plvect with the pltr2 function as the
pltr. This only affects the location of the vectors, not the direction /
magnitude.
The only reason for plvec2 e
On Wed, Dec 12, 2007 at 09:20:46AM +0100, Arjen Markus wrote:
> Andrew Ross wrote:
>
> >plvec2 is equivalent to calling plvect with the pltr2 function as the
> >pltr. This only affects the location of the vectors, not the direction /
> >magnitude.
> >
> >The only reason for plvec2 etc is that for
Andrew Ross wrote:
>plvec2 is equivalent to calling plvect with the pltr2 function as the
>pltr. This only affects the location of the vectors, not the direction /
>magnitude.
>
>The only reason for plvec2 etc is that fortran (and several other bindings)
>don't allow you to pass a function name a
