#14560: libXt-1.2.1
-------------------------+-----------------------
 Reporter:  renodr       |       Owner:  renodr
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  10.1
Component:  BOOK         |     Version:  SVN
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+-----------------------

Comment (by renodr):

 {{{
 Matt Turner (1):
       libXt 1.2.1

 Thomas E. Dickey (72):
       update to 1.1.5.3 to reflect documentation updates/review
       fix a typo
       use _X_UNUSED to quiet compiler warnings
       constify table passed to _XtTableAddConverter to reduce strict
 compiler warnings
       fix a possibly-uninitialized quark, and remove unnecessary casts
 which produced warnings
       remove/amend a few casts which produced warnings
       fix a couple of strict warnings by refactoring macros
       add curly-braces in a couple of places to allow running "indent"
       indent'd like "x-indent.sh", but with a more complete set of
 typedefs - see
       turn off indent in generated files
       remove the ARGUSED lines, which confuse GNU indent, ditto for
 LINTLIBRARY
       bump minor version to reflect code-cleanup
       improved the script used for typedef-options with indent, updated
 indentation
       issue 12 - DISPLAY=:0.-1 XtScreenDatabase segfault
       new build
       issue #12: work within existing interface which attempts to obtain
 the
       add a null-pointer check, overlooked in fix for issue #12.
       _XtCalloc actually uses a Cardinal, not size_t

 Walter Harms (3):
       no need to check arguments for XtFree()
       refactoring, reduce indent level
       add errorhandling to _XtVaToTypedArgList()

 git tag: libXt-1.2.1
 }}}

--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/14560#comment:2>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to