Programming" lại đi coding tiếp.
Không có vẻ gì là bác này quên code C cả, dù sinh năm 1957 ;)
Anyway, lib này có lẽ ít quan trọng.
Mình dùng jpeg và png nhiều hơn.
Đúng ra, png được tạo ra để thay thế gif bởi những vấn đề pháp lý và gif gây ra.
Điều này rất đúng vào thời kỳ đầu của Internet khi IE còn bá chủ và
gif, với dung lượng nhỏ
và hiển thị được transparent background là bá chủ.
Nhưng bây giờ có lẽ đã không còn đúng nữa thì PNG, HTML 5 và nhiều
công nghệ khác nữa đã thay thế được gif.
Btw, còn bác nào dùng GIF không nhỉ?
---------- Forwarded message ----------
From: Eric S. Raymond <esr@>
Date: Tue, Apr 24, 2012 at 09:02
Subject: [giflib-devel] State of the giflib code - what else can I remove?
To: giflib-devel@
Cc: Toshio Kuratomi <a.badger@>
The giflib codebase badly needed to be brought into the 21st century.
Significant portions of it were obsolete and a maintainance burden, and
the C it was written in was a rather archaic dialect tangled with platform
#ifdefs - so old that it didn't rely on having void * or fixed-width types.
I've already fixed a lot of the more obvious problems simply by
ripping out a lot of obsolescent code. C99 and Single Unix
Specification give us better ways to do cross-platform things that
used to take a lot of platform-specific headers. I've also dropped
a couple of utilities, gif2epsn and gif2iris, that targeted obsolete
hardware.
The only potentially user-visible change to the library so far is that
the undocumented DumpScreen2Gif() entry point is gone. Most of that
code was certainly obsolete, targeting things like EGA graphic cards
(!). Only the X case might still have worked, and I'm doubtful about
even that much. Ripping it out solved about 80% of the remaining
portability problems.
The remaining 20% are concentrated in a small number of files that
I'm wondering if I should just drop.
1, gif2x11. Do we really need to carry an X viewer in the giflib
distribution? There are enough of those that I'm inclined to let
that be somebody else's problem.
2. The Game Boy Advanced support. What's up with that? Was it ever
documented? The product was discontinued in 2008 - is there any reason
to consider it relevant to future giflib releases?
3. The files in the windows/ directory. Where are these documented?
Why are we carrying them? I see the code dates from 1999; is there
any reason to believe anyone is still using it?
--
>>esr>>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
giflib-devel mailing list
giflib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/giflib-devel
--
Best Regards,
Nguyen Hung Vu [aka: NVH] ( in Vietnamese: Nguyễn Vũ Hưng )
vuhung16plus{remove}@gmail.dot.com , YIM: vuhung16 , Skype:
vuhung16plus, twitter: vuhung, MSN: vuhung16.
http://www.facebook.com/nguyenvuhung
http://nguyen-vu-hung.blogspot.com/
Học tiếng Nhật: http://hoc-tiengnhat.blogspot.com/
Vietnamese LibreOffice: http://libo-vi.blogspot.com/
Mozilla & Firefox tiếng Việt: http://mozilla-vi.blogspot.com/
Disclaimer: When posted to social networking groups include, but not
limited Linux Users' Groups,
Free and Open Sources forums, mailing lists, the obove is my personal
opinion and is *not*
the opinion of my employer(s), associations and/or groups I join.
No comments:
Post a Comment