help-octave
[Top][All Lists]
Advanced

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

Re: Fixed point shift


From: David Bateman
Subject: Re: Fixed point shift
Date: Thu, 25 Nov 2004 10:02:40 +0100
User-agent: Mutt/1.4.1i

According to John W. Eaton <address@hidden> (on 11/25/04):
> On 25-Nov-2004, David Bateman <address@hidden> wrote:
> 
> | I didn't create the equivalent operators/functions in the other three
> | classes. Also, the bitshift stuff is handled through a function called
> | bitshift in octave rather than with a "<<" or ">>" operator which have
> | other meanings in octave (file i/o). 
> 
> Since these are binary operators, you could overload them for
> bitshifing as well (I/O requires the left operand to be a stream
> object).

I think this is a good idea. The only thing is that if you want to
specify the mask then you need the third argument of bitshift. However,
it is a rare case that that is used....

However to make this easier the macro DO_BITSHIFT in bitfcns.cc
would need to be rewritten as a template function so that they are
available to the operators instead of just through Fbitshift as they
are now..

Cheers
David

-- 
David Bateman                                address@hidden
Motorola CRM                                 +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax) 
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------



reply via email to

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