gnustep/libs-base
0
0
Fork 0
mirror of https://github.com/gnustep/libs-base.git synced 2025-04-23 09:04:13 +00:00
Code Issues Projects Releases Packages Wiki Activity

doc tweaks

Browse source 
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/libs/base/trunk@38124 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
Richard Frith-MacDonald 2014-10-19 09:50:29 +00:00
parent 3a6f7d4df2
commit f4bb557983
6 changed files with 25 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
ANNOUNCE
View file

@ -21,7 +21,8 @@ portion of the OpenStep standard (the Foundation library).
1.2 Noteworthy changes in version `1.24.7'
==========================================
* TLS and other security improvements
* TLS and other security improvements (note, SSLv3.0 is disabled by
default in order to prevent the 'POODLE' attack).
* Latest timezone data included

2
Documentation/GNUmakefile
View file

@ -58,7 +58,7 @@ SUBPROJECTS = manual General
DOCUMENT_TEXT_NAME = \
INSTALL NEWS README ANNOUNCE
TOP_DOC_FILES = INSTALL NEWS README ANNOUNCE README.initialize
TOP_DOC_FILES = INSTALL NEWS README ANNOUNCE
gnustep-base_TEXI_FILES = \
version.texi \

7
Documentation/README.initialize
View file

@ -1,7 +0,0 @@
The libobjc included with gcc does not have a thread-safe implementation of the initialize method. This means that any classes not already used may be incorrectly initialised, potentially causing strange behaviors and crashes.
To put this into context, the runtime bug has been knoown for several years and only rarely causes problems ... the easy workaround being to ensure that any classes used by a new thread have already been used in the main thread before the new thread starts.
If you are worried, please build/run GNUstep with a runtime which supports the +initialize method. The GNUstep stable runtime (libobjc) and experimental runtime (libobjc2), available from the GNUstep website and subversion repository, should both work.
To disable this warning (eg. for an application which does not suffer any problems caused by this runtime bug), please set the GSSilenceInitializeWarning user default to YES.");

3
Documentation/news.texi
View file

@ -14,7 +14,8 @@ See the @url{ReleaseNotes.html} document for more information.
@section Noteworthy changes in version @samp{1.24.7}
@itemize @bullet
@item TLS and other security improvements
@item TLS and other security improvements (note, SSLv3.0 is disabled by default
in order to prevent the 'POODLE' attack).
@item Latest timezone data included
@item Various other bugfixes
@end itemize

3
NEWS
View file

@ -8,7 +8,8 @@ See the `ReleaseNotes.html' document for more information.
1.1 Noteworthy changes in version `1.24.7'
==========================================
* TLS and other security improvements
* TLS and other security improvements (note, SSLv3.0 is disabled by
default in order to prevent the 'POODLE' attack).
* Latest timezone data included

18
README.initialize Normal file
View file

@ -0,0 +1,18 @@
The libobjc included with older versions of gcc does not have a thread-safe
implementation of the initialize method. This means that any classes not
already used may be incorrectly initialised, potentially causing strange
behaviors and crashes.
To put this into context, the runtime bug has been known for several years
and only rarely causes problems ... the easy workaround being to ensure that
any classes used by a new thread have already been used in the main thread
before the new thread starts.
If you are worried, please build/run GNUstep with a runtime which supports
the +initialize method. The GNUstep stable runtime (libobjc) and experimental
runtime (libobjc2), available from the GNUstep website and subversion
repository, should both work.
To disable this warning (eg. for an application which does not suffer any
problems caused by this runtime bug), please set the GSSilenceInitializeWarning
user default to YES.");