octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #45945] Missing Matlab's special support for i


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #45945] Missing Matlab's special support for int64/uint64 integer literals
Date: Mon, 22 Aug 2016 21:24:53 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0

Update of bug #45945 (project octave):

                 Summary: Missing Matlab's special support for integer
literals => Missing Matlab's special support for int64/uint64 integer literals

    _______________________________________________________

Follow-up Comment #20:

I some results back from someone with Matlab R2014. The script tested
constructions like this


int64(9223372036854775804)
int64(9223372036854775804*1)
int64(9223372036854775804)*1
int64([9223372036854775803;9223372036854775804])
builtin('int64', 9223372036854775804)
myfcn = @int64;
myfcn(9223372036854775804)
int64 = @abs;
int64(9223372036854775804)


Only when a single literal number is enclosed within the parentheses, and only
when the function being called is actually the function int64, is the value
interpreted as an int64 literal value. These are the 1st and 3rd cases above.
In all other cases, the value is parsed and stored as a double value first and
passed to the int64 function (or abs function in the last case) as a
double-valued argument.

In particular, the last case does *not* parse its argument as an int64
literal, even though to the parser it looks identical to the first case.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45945>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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