[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #30423] Incorrect limit for array sizes?

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #30423] Incorrect limit for array sizes?
Date: Tue, 20 Jul 2010 15:47:59 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100501 Iceweasel/3.5.9 (like Firefox/3.5.9)

Follow-up Comment #2, bug #30423 (project octave):

Unless there is a good reason (as you say, there may be), I would expect to
be able to index elements 1 to intmax ('int32') if octave_idx_type is int32_t.
 Likewise for int64.

I can accept a smaller limit provided that it is documented to avoid future
confusion.  I know I was confused that I couldn't allocate an array with
intmax ('int32') elements.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]