I identified 2 bugs in the way that the "images.gif" vocab parses the
GIF file format.

1) The Image Descriptor block label (0x2c) was being read twice from
the stream: once to do the dispatch to parse the block and again to
store it in the image-descriptor tuple's "separator" slot. The
separator slot is not needed since it is really just a label that is
needed during parsing.

2) When parsing the actual image data inside the Image Descriptor
block, the LZW minimum code size byte was read as if it was the Block
Size, but in fact, the Block Size is stored in the following byte.

The diff is attached.

Doug, if you don't mind, I think I will try writing the GIF decoder today.

-keith

Attachment: gif-bugfix.diff
Description: Binary data

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk

Reply via email to