Re: Plans for gnuplot version 5

[<pl...@pi...>]

On 04/15/14 22:24, Marek Peca wrote:
>
>> I don't think we're supporting any systems or OSes without an FPU
>> anymore, right? And memory or CPU are not nearly the limitations they
>> once were (at that level). Maybe v5 is the time gnuplot should stop
>> treating integer-looking numbers like integers unless requested
>> explicitly via int()?
>
> Well, have you just offered breaking the behaviour for all the existing
> scripts, which may rely on the default integer treatment?
>
> Maybe it could be changed, but in this case, I'd strongly vote for
> at least maintaining a compatibility flag (cmdline arg, setting variable).
> Still, I am afraid it can make some harm.
>
> Regards,
> Marek
>

Hi

Clearly this will be a major compatibility issue , which is why it is 
being brought up in relation to v5 when this requirement is being 
relaxed to allow worthwhile changes that would otherwise be forbidden by 
the usual strict compatibility policy.

Coming from a background of strong typed languages I do find this rather 
fuzzy typing particularly infuriating.

I can't really think of a context in which there is a use for integer 
arithmetic other than the integer division which would be much clearer 
if it was coded with int() , anyway.

There must be a lot of users who don't even know what integer arithmetic 
is about these days. Should they really have to learn to be able to use 
gnuplot ?

It does seem rather arcane and of no real benefit. Maybe this is a good 
to get rid of it.

I use gnuplot on embedded ARM platforms that do not have an FPU and have 
to use inefficient software emulation of floating point. In view of the 
volume of fp involved in producing a plot, i don't think the odd int 
division would matter. However, it could conceivable be an argument for 
some of these platforms in other cases than my own.

Obviously a compiler compatibility switch would be a good idea for those 
who have considerable investment in gnuplot scripts that they do not 
wish to rewrite and re-debug.

Generally, I think removing integer division is a good proposition.

regards, Peter.