Re: [Rd] error messages because of integer overflow

2004-02-19 Thread Prof Brian Ripley
On 20 Feb 2004, Peter Dalgaard wrote: > Prof Brian Ripley <[EMAIL PROTECTED]> writes: > > > All of these stem from the use of constructions like > > > > len = asInteger(CADR(args)); > > > > and a failure to check the return value for NA. > > > > We'll add suitable checks, so don't bother w

Re: [Rd] error messages because of integer overflow

2004-02-19 Thread Peter Dalgaard
Prof Brian Ripley <[EMAIL PROTECTED]> writes: > All of these stem from the use of constructions like > > len = asInteger(CADR(args)); > > and a failure to check the return value for NA. > > We'll add suitable checks, so don't bother with a bug report. We should probably take notice that th

Re: [Rd] error messages because of integer overflow

2004-02-19 Thread Prof Brian Ripley
All of these stem from the use of constructions like len = asInteger(CADR(args)); and a failure to check the return value for NA. We'll add suitable checks, so don't bother with a bug report. On Thu, 19 Feb 2004, Uwe Ligges wrote: > This might be worth a wishlist/bug report (I'll submit it

[Rd] error messages because of integer overflow

2004-02-19 Thread Uwe Ligges
This might be worth a wishlist/bug report (I'll submit it as such if nobody disagrees). The following objects are nonsense in a way (too huge). It may happen, that you have got a bug in your code that generates such objects, so it would be great to get another error message telling the problem