On Mon, 2 May 2005 [EMAIL PROTECTED] wrote:

> /home/pjk/mjpegplay/y4mdenoise/DoublyLinkedList.hh: undefined reference to 
> `Limits<unsigned>::Log2Bits'
> 
> This arises from the use of "unsigned int" in file  
> y4mdenoise/BitmapRegion2D.hh class 
> function
> BitmapRegion2D<INDEX,SIZE>::IteratorForward
> if this is replace with "uint32_t" then  everything compiles.
> The problem is I do not understand this code well enough to know if this is 
> reasonable. 
> Unsigned int is used frequently throughout this file, perhaps all should be 
> addressed?

        Yes, I noticed that as well - other uses of 'unsigned int' are not
        causing any problem.  I hesitate to change things that aren't causing
        problems - often that's a way to create new problems ;)

        In BitmapRegion2D.hh I see 4 uses of 'unsigned int' with Log2Bits:

BitmapRegion2D.hh:      tnWordIndex = tnBitIndex >> Limits<unsigned 
int>::Log2Bits;
BitmapRegion2D.hh:      tnBitIndex -= tnWordIndex << Limits<unsigned 
int>::Log2Bits;
BitmapRegion2D.hh:      tnLastWordIndex = tnLastBitIndex >> Limits<unsigned 
int>::Log2Bits;
BitmapRegion2D.hh:      tnLastBitIndex -= tnLastWordIndex << Limits<unsigned 
int>::Log2Bits;

        Are those the same 4 that you needed to change?

        For now even the x86_64 systems have 'unsigned int' as 32bits - offhand
        I do not know of a (popular) system that has 'unsigned int' being
        64bits so it's probably OK to change those 4 uses of unsigned in
        to be uint32_t.

        Cheers,
        Steven Schultz



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Mjpeg-users mailing list
Mjpeg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mjpeg-users

Reply via email to