On Sat, Aug 18, 2007 at 02:10:46PM -0700, Alan Irwin wrote:
> This recent screw-up on my part in even the most minimal maintenance of the
> deprecated autotools build system, the zero testing we all gave that system
> afterwards, and the lack of a volunteer who wants to maintain or even test
> tha
Works for me. Although some suitable phrasing to distinguish between
plwarn and plabort would be be good. plabort is aborting the function
so will probably produce odd results, but it is not fatal and is not
aborting whole program.
Andrew
> On Sat, Aug 18, 2007 at 02:19:38PM -0700, Alan Irwin w
On 2007-08-20 10:37+0100 Andrew Ross wrote:
>
> Works for me. Although some suitable phrasing to distinguish between
> plwarn and plabort would be be good. plabort is aborting the function
> so will probably produce odd results, but it is not fatal and is not
> aborting whole program.
I have had
Andrew Ross writes:
>
> Works for me. Although some suitable phrasing to distinguish between
> plwarn and plabort would be be good. plabort is aborting the function
> so will probably produce odd results, but it is not fatal and is not
> aborting whole program.
Sorry for not responding unt
On 2007-08-20 13:06-0500 Maurice LeBrun wrote:
> Andrew Ross writes:
> >
> > Works for me. Although some suitable phrasing to distinguish between
> > plwarn and plabort would be be good. plabort is aborting the function
> > so will probably produce odd results, but it is not fatal and is not
> > a
Alan W. Irwin writes:
> Maurice and Geoffrey, please correct this if I have it wrong, but I believe
> plwarn should be reserved for a warning where there is a reasonable fixup
> available (e.g., "Driver does not support hardware solid fills, switching to
> software fill.\n"), plabort should be
On 2007-08-20 17:32-0500 Maurice LeBrun wrote:
> While a call to plabort() may represent an internal plplot error, the fact
> that it is not fatal nor necessarily interfering with future plot calls makes
> it difficult to justify any error code set upon exit.
There is the ctest downside, but ther
Hi Andrew:
Right after I sent off the last message going along with Maurice's wishes
about no returned error code for plabort, I realized there is a good option
to get ctest right without affecting the PLplot core; return from the
test_xxx.sh scripts with a non-zero status code if any command outp
Andrew Ross writes:
>
> On Sat, Aug 18, 2007 at 02:10:46PM -0700, Alan Irwin wrote:
> > This recent screw-up on my part in even the most minimal maintenance of the
> > deprecated autotools build system, the zero testing we all gave that system
> > afterwards, and the lack of a volunteer who w
(trying to catch up on email)
Alan W. Irwin writes:
> Once -ori 0, -ori 1, -ori 2, etc., work, then for fun try -ori 0.3 (i.e.,
> non-integer -ori values). You will find a long-standing PLplot bug for that
> case which doesn't give correct plotted results (the rectangular viewport
> gets shea
On 2007-08-20 21:35-0500 Maurice LeBrun wrote:
> > On Sat, Aug 18, 2007 at 02:10:46PM -0700, Alan Irwin wrote:
> > > [...] so long as we give some advance notice. Thefore, I think immediately
> > > after 5.8.0 would be appropriate so that our first release in the 5.9.x
> > > series and all develop
11 matches
Mail list logo
