From ed05ef427660b76aa83c3c84e2a269a1ef1d0a6c Mon Sep 17 00:00:00 2001 From: Ivan Maidanski Date: Sat, 15 Dec 2012 01:03:50 +0400 Subject: [PATCH] Replace '`' symbol with double-quote in comments * doc/README.win32: Replace "`" symbol (and paring single-quote) with double-quote symbol. * dyn_load.c (GC_register_dynlib_callback): Likewise. * finalize.c (GC_should_invoke_finalizers): Likewise. * include/private/gc_priv (GC_INLINE, ptr_t): Likewise. * include/private/gcconfig.h (DATAEND): Likewise. --- doc/README.win32 | 2 +- dyn_load.c | 2 +- finalize.c | 2 +- include/private/gc_priv.h | 4 ++-- include/private/gcconfig.h | 8 ++++---- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/doc/README.win32 b/doc/README.win32 index d14686dd..471126e2 100644 --- a/doc/README.win32 +++ b/doc/README.win32 @@ -134,7 +134,7 @@ To compile the collector and testing programs use the command: All programs using gc should be compiled with 4-byte alignment. For further explanations on this see comments about Borland. -If the gc is compiled as dll, the macro ``GC_DLL'' should be defined before +If the gc is compiled as dll, the macro "GC_DLL" should be defined before including "gc.h" (for example, with -DGC_DLL compiler option). It's important, otherwise resulting programs will not run. diff --git a/dyn_load.c b/dyn_load.c index b1ec6014..9d9700fe 100644 --- a/dyn_load.c +++ b/dyn_load.c @@ -446,7 +446,7 @@ STATIC int GC_register_dynlib_callback(struct dl_phdr_info * info, case PT_GNU_RELRO: /* This entry is known to be constant and will eventually be remapped read-only. However, the address range covered by this entry is - typically a subset of a previously encountered `LOAD' segment, so + typically a subset of a previously encountered "LOAD" segment, so we need to exclude it. */ { int j; diff --git a/finalize.c b/finalize.c index 63696699..0ca956a4 100644 --- a/finalize.c +++ b/finalize.c @@ -954,7 +954,7 @@ GC_INNER void GC_finalize(void) #endif /* !JAVA_FINALIZATION_NOT_NEEDED */ /* Returns true if it is worth calling GC_invoke_finalizers. (Useful if */ -/* finalizers can only be called from some kind of `safe state' and */ +/* finalizers can only be called from some kind of "safe state" and */ /* getting into that safe state is expensive.) */ GC_API int GC_CALL GC_should_invoke_finalizers(void) { diff --git a/include/private/gc_priv.h b/include/private/gc_priv.h index 58b22e1b..f800f090 100644 --- a/include/private/gc_priv.h +++ b/include/private/gc_priv.h @@ -145,7 +145,7 @@ typedef char * ptr_t; /* A generic pointer to which we can add */ #endif /* __GNUC__ */ #ifdef HAVE_CONFIG_H - /* The `inline' keyword as determined by Autoconf's `AC_C_INLINE'. */ + /* The "inline" keyword is as determined by Autoconf's AC_C_INLINE. */ # define GC_INLINE static inline #elif defined(_MSC_VER) || defined(__INTEL_COMPILER) || defined(__DMC__) \ || defined(__WATCOMC__) @@ -233,7 +233,7 @@ typedef char * ptr_t; /* A generic pointer to which we can add */ /* 1. There are probably no interesting, portable, */ /* strictly ANSI conforming C programs. */ /* 2. This option makes it hard for the collector */ - /* to allocate space that is not ``pointed to'' */ + /* to allocate space that is not "pointed to" */ /* by integers, etc. Under SunOS 4.X with a */ /* statically linked libc, we empirically */ /* observed that it would be difficult to */ diff --git a/include/private/gcconfig.h b/include/private/gcconfig.h index c21c38ca..ceceb5b0 100644 --- a/include/private/gcconfig.h +++ b/include/private/gcconfig.h @@ -600,11 +600,11 @@ * On UNIX-like systems, the collector will scan the area between DATASTART * and DATAEND for root pointers. * - * DATAEND, if not `end' where `end' is defined as ``extern int end[];''. + * DATAEND, if not "end", where "end" is defined as "extern int end[]". * RTH suggests gaining access to linker script synth'd values with - * this idiom instead of `&end' where `end' is defined as ``extern int end;'' . - * Otherwise, ``GCC will assume these are in .sdata/.sbss'' and it will, e.g., - * cause failures on alpha*-*-* with ``-msmall-data or -fpic'' or mips-*-* + * this idiom instead of "&end", where "end" is defined as "extern int end". + * Otherwise, "GCC will assume these are in .sdata/.sbss" and it will, e.g., + * cause failures on alpha*-*-* with -msmall-data or -fpic or mips-*-* * without any special options. * * STACKBOTTOM is the cool end of the stack, which is usually the -- 2.50.1