2.6.0GLIB_2_6_0

1 files changed, 15 insertions, 15 deletions

diff --git a/README.in b/README.in
index 177d63a99..5a1ce5eb1 100644
--- a/README.in
+++ b/README.in
@@ -32,7 +32,7 @@ Notes about GLib 2.6.0
   returning or accepting pathnames have been changed to expect
   filenames in this encoding, and the common POSIX functions dealing
   with pathnames have been wrapped. These wrappers are declared in the
-  header <glib/gstdio.h> which must be included explicitly, it is not
+  header <glib/gstdio.h> which must be included explicitly; it is not
   included through <glib.h>.
 
   On current (NT-based) Windows versions, where the on-disk file names
@@ -52,9 +52,9 @@ Notes about GLib 2.6.0
   consideration, and use the gstdio wrappers to access files whose
   names have been constructed from strings returned from GLib.
 
-* Likewise, g_get_user_name() and g_get_real_name() have been changed to return
-  UTF-8 on Windows, while keeping the old semantics for applications compiled
-  against older versions of GLib.
+* Likewise, g_get_user_name() and g_get_real_name() have been changed 
+  to return UTF-8 on Windows, while keeping the old semantics for 
+  applications compiled against older versions of GLib.
 
 * The GLib uses an '_' prefix to indicate private symbols that
   must not be used by applications. On some platforms, symbols beginning 
@@ -63,10 +63,10 @@ Notes about GLib 2.6.0
   GLib+ 2.6 makes several symbols private which were not in any installed 
   header files and were never intended to be exported.
 
-* GLib uses a technique involving macros for reducing the amount of PLT
-  redirections which has the side effect that the names of internally used
-  GLib functions are prefixed with IA__. The g_return_if_fail() macros
-  strip this prefix away, but it will show up e.g. in a debugger.
+* To reduce code size and improve efficiency, GLib, when compiled 
+  with the GNU toolchain, has separate internal and external entry 
+  points for exported functions. The internal names, which begin with 
+  IA__, may be seen when debugging a GLib program.
 
 * On Windows, GLib no longer opens a console window when printing
   warning messages if stdout or stderr are invalid, as they are in
@@ -74,11 +74,11 @@ Notes about GLib 2.6.0
   stderr if you need to see them.
 
 * The child watch functionality tends to reveal a bug in many
-  thread implementations (in particular the older LinuxThreads implementation
-  on Linux) where it's not possible to call waitpid() for a child
-  created in a different thread. For this reason, for maximum portability,
-  you should structure your code to fork all child processes that you want
-  to wait for from the main thread.
+  thread implementations (in particular the older LinuxThreads 
+  implementation on Linux) where it's not possible to call waitpid() 
+  for a child created in a different thread. For this reason, for 
+  maximum portability, you should structure your code to fork all 
+  child processes that you want to wait for from the main thread.
 
 * A problem was recently discovered with g_signal_connect_object(); 
   it doesn't actually disconnect the signal handler once the object being 
@@ -104,8 +104,8 @@ In the bug report please include:
 
 * How to reproduce the bug. 
 
-  If you can reproduce it with the testgtk program that is built 
-  in the gtk/ subdirectory, that will be most convenient.  Otherwise, 
+  If you can reproduce it with one of the test programs that are built 
+  in the tests/ subdirectory, that will be most convenient.  Otherwise, 
   please include a short test program that exhibits the behavior. 
   As a last resort, you can also provide a pointer to a larger piece 
   of software that can be downloaded.