JANITORIAL: Fix some typos in comments

binutils/2.23.2/patches/0001-Changes-for-various-Amiga-targets.patch

@@ -1375,7 +1375,7 @@ index 0000000000000000000000000000000000000000..9d715d64d458e6599c19ed65fbb61c25
 +	  break;
 +
 +	default:
-+	  /* Something very nasty happened: invalid hunk occured... */
++	  /* Something very nasty happened: invalid hunk occurred... */
 +	  bfd_set_error (bfd_error_wrong_format);
 +	  return FALSE;
 +	  break;
@@ -3913,7 +3913,7 @@ index 0000000000000000000000000000000000000000..9067a0a06b933c67bfd3542b299d1adb
 +This is not the case with a.out formats, so there relocations can be applied at link time,
 +not at run time, like on the Amiga.
 +The special routines compensate this: instead of applying the relocations, they are
-+copied to the output file, if neccessary.
++copied to the output file, if necessary.
 +As as consequence, @code{final_link} and @code{get_relocated_section_contents} are nearly identical to
 +the original routines from @file{linker.c} and @file{reloc.c}.
 +*/
@@ -27426,7 +27426,7 @@ index bc2dd491592e56fb664cdf96fc32491c08e1e075..bc40541b7c5aecc30a7a74fd61f29225
  };
 
  /* Name of register halves for MAC/EMAC.
-    Seperate from reg_names since 'spu', 'fpl' look weird.  */
+    Separate from reg_names since 'spu', 'fpl' look weird.  */
  static char *const reg_half_names[] =
 -- 
 2.30.2

binutils/2.23.2/patches/0002-Fixed-errors-occuring-with-more-recent-versions-of-t.patch

@@ -1,7 +1,7 @@
 From 46bf473f82fa04bdb21d752fc45daca5690bc1ea Mon Sep 17 00:00:00 2001
 From: Sebastian Bauer <mail@sebastianbauer.info>
 Date: Sat, 29 Nov 2014 11:32:22 +0100
-Subject: [PATCH 02/13] Fixed errors occuring with more recent versions of
+Subject: [PATCH 02/13] Fixed errors occurring with more recent versions of
  texinfo.
 
 ---

binutils/2.23.2/patches/0006-Introduced-strip-unneeded-rel-relocs.patch

@@ -5,7 +5,7 @@ Subject: [PATCH 06/13] Introduced strip-unneeded-rel-relocs.
 
 Normally, on AmigaOS we keep all relocs for executables as we don't have
 an isolated address space. However, not all relative relocs are necessary
-to be kept, for instance if they are refering to the same program section.
+to be kept, for instance if they are referring to the same program section.
 With the newly introduced strip option --strip-unneeded-rel-relocs these
 can be removed now.
 ---
@@ -87,7 +87,7 @@ index 88bd071eefa8b5426eaadfd6431e9de5d4a4591b..4beee77179b85479d5b43507d9eb2a6e
 +		/* Don't keep the symbol, but keep the reloc unless it is a relative reloc that is
 +		 * requested by the user to be removed. For now, we also don't discard the reloc if
 +		 * its targeting a different section. This can happen for relocs in the .rodata
-+		 * segment that refering to the .text segment. AmigaOS will possibly split these
++		 * segment that referring to the .text segment. AmigaOS will possibly split these
 +		 * up.
 +		 */
 +		if (!strip_unneeded_rel_relocs || !relpp [i]->howto->pc_relative || sec->index != osection->index)

binutils/2.23.2/patches/0010-Fix-Wimplicit-fallthrough-warnings.patch

@@ -79,9 +79,9 @@ index 52c884cd83d95745e512b4ce04caec23a94b496d..c845164f6c6ad245174c0013b7a13da4
        free (compressed_buffer);
        sec->contents = uncompressed_buffer;
        sec->compress_status = COMPRESS_SECTION_DONE;
--      /* Fall thru */
+-      /* Fall through */
  #endif
-+      /* Fall thru */
++      /* Fall through */
 
      case COMPRESS_SECTION_DONE:
        if (p == NULL)
@@ -118,7 +118,7 @@ index fa9333b7f1d953b5ebcf338bd465c75f99842bb3..4f0c37c97accbb9a00762fc2e04c56ea
  	case R_PPC_UADDR16:
  	  if (info->shared)
  	    break;
-+	  /* Fall thru */
++	  /* Fall through */
 
  	case R_PPC_PLT32:
  	case R_PPC_PLTREL24:
@@ -136,7 +136,7 @@ index 5c92c53da7b3dec8f85a0a0b930190635f89dcfb..9166631ac66055c2621682b157f741bf
  	case R_PPC_UADDR16:
  	  if (info->shared)
  	    break;
-+	  /* Fall thru */
++	  /* Fall through */
 
  	case R_PPC_PLT32:
  	case R_PPC_PLTREL24:

binutils/2.23.2/patches/0012-Fix-pointer-comparision-bug.patch

@@ -1,7 +1,7 @@
 From 3ce5beb5610ded6b50cac4fd492506ce74f71d0e Mon Sep 17 00:00:00 2001
 From: Sebastian Bauer <mail@sebastianbauer.info>
 Date: Sun, 8 Jul 2018 15:37:39 +0200
-Subject: [PATCH 12/13] Fix pointer comparision bug.
+Subject: [PATCH 12/13] Fix pointer comparison bug.
 
 ---
  binutils/stabs.c | 2 +-

gcc/10/patches/0001-Changes-for-AmigaOS-version-of-gcc.patch

@@ -136,7 +136,7 @@ index e67c71a50e7fdc1e1380856ea10787e4f33b338c..803590e45b97ca0cc7b6dba2568f4112
  	                      attr_warn_unused_result_exclusions },
 +  { "libcall",                0, 0, false, true, true, false,
 +                              handle_libcall_attribute, NULL },
-+  /* Similiar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
++  /* Similar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
 +  { "libcall2",               0, 0, false, true, true, false,
 +                              handle_libcall_attribute, NULL },
    { "sentinel",               0, 1, false, true, true, false,
@@ -1848,7 +1848,7 @@ index c4d7cdb6fa7a32e4731bde5724277c5a53a7dfbd..a8b01d72a3fc7553b72a62b683033fdb
 +;; generated instead of elf_base_low. Since the requirements for elf_base_low
 +;; are more restrictive than those for elf_low, there should be no problems
 +;; when determining which instruction to use. Additionally, the elf_low function
-+;; has now been guared against used accidently.
++;; has now been guared against used accidentally.
 +(define_insn "elf_base_high"
 +  [(set (match_operand:SI 0 "gpc_reg_operand" "=b")
 +        (plus:SI (match_operand:SI 1 "gpc_reg_operand" "b")

gcc/10/patches/0007-Some-AmigaOS-4.x-compability-changes-for-posix-threa.patch

@@ -1,7 +1,7 @@
 From eb8b8a2708023813b9a42be4c97393b04f4998c3 Mon Sep 17 00:00:00 2001
 From: Sebastian Bauer <mail@sebastianbauer.info>
 Date: Thu, 21 Jan 2016 20:46:59 +0100
-Subject: [PATCH 07/33] Some AmigaOS 4.x compability changes for posix thread
+Subject: [PATCH 07/33] Some AmigaOS 4.x compatibility changes for posix thread
  support.
 
 ---

gcc/10/patches/0017-Avoid-section-anchors-in-the-baserel-mode.patch

@@ -38,7 +38,7 @@ index 85c03f28e37d64865360692a14fcc8a197b55395..a7cfaaa2ca4ac913d78e3240aa994a65
 +
 +/* Addititionally to the normal anchor (optimization) suppression, suppress
 + * it also in the baserel mode because we don't adjust the anchor access yet.
-+ * It would make some sence to support anchros also in baserel mode, because
++ * It would make some sense to support anchors also in baserel mode, because
 + * baserel access is 32 bit.
 + */
 +bool

gcc/10/patches/0022-Provide-a-documentation-for-checktags-and-tagtype-at.patch

@@ -24,7 +24,7 @@ index 9466c857b276d1eab3cd7117cc7dcf102cbb2acd..0a4aded9e28977f4df1a7c6cb8d21a8c
 +@cindex @code{checktags} function attribute
 +The @code{checktags} tells the some parameters of the function are
 +taglists. In turn it will enable tag-type checking at compile-time, by
-+leveraging the extra information provded to enum-defined tags to which
++leveraging the extra information provided to enum-defined tags to which
 +a @code{tagtype} attribute is associated. The check assumes that if a
 +parameter is an integer constant to which a type is associated, then
 +it must be followed by an argument of that type. If that is not the

gcc/11/patches/0001-Changes-for-AmigaOS-version-of-gcc.patch

@@ -136,7 +136,7 @@ index cdf89d66fe14281cffb2dc1c8c0bae9547afb2a5..4f2176afc9e57be9ed17624680ee36a7
  	                      attr_warn_unused_result_exclusions },
 +  { "libcall",                0, 0, false, true, true, false,
 +                              handle_libcall_attribute, NULL },
-+  /* Similiar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
++  /* Similar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
 +  { "libcall2",               0, 0, false, true, true, false,
 +                              handle_libcall_attribute, NULL },
    { "sentinel",               0, 1, false, true, true, false,
@@ -1848,7 +1848,7 @@ index a4a7d105f5e2d3e7d86916f736c0a8c51e371ed9..1d023f596e4431d78bce018f4c27961d
 +;; generated instead of elf_base_low. Since the requirements for elf_base_low
 +;; are more restrictive than those for elf_low, there should be no problems
 +;; when determining which instruction to use. Additionally, the elf_low function
-+;; has now been guared against used accidently.
++;; has now been guarded against being used accidentally.
 +(define_insn "elf_base_high"
 +  [(set (match_operand:SI 0 "gpc_reg_operand" "=b")
 +        (plus:SI (match_operand:SI 1 "gpc_reg_operand" "b")

gcc/11/patches/0007-Some-AmigaOS-4.x-compability-changes-for-posix-threa.patch

@@ -1,7 +1,7 @@
 From 6c249f64bd2d0ebf30f51531484ea1742962ee12 Mon Sep 17 00:00:00 2001
 From: Sebastian Bauer <mail@sebastianbauer.info>
 Date: Thu, 21 Jan 2016 20:46:59 +0100
-Subject: [PATCH 07/39] Some AmigaOS 4.x compability changes for posix thread
+Subject: [PATCH 07/39] Some AmigaOS 4.x compatibility changes for posix thread
  support.
 
 ---

gcc/11/patches/0017-Avoid-section-anchors-in-the-baserel-mode.patch

@@ -38,7 +38,7 @@ index 85c03f28e37d64865360692a14fcc8a197b55395..a7cfaaa2ca4ac913d78e3240aa994a65
 +
 +/* Addititionally to the normal anchor (optimization) suppression, suppress
 + * it also in the baserel mode because we don't adjust the anchor access yet.
-+ * It would make some sence to support anchros also in baserel mode, because
++ * It would make some sense to support anchors also in baserel mode, because
 + * baserel access is 32 bit.
 + */
 +bool

gcc/11/patches/0022-Provide-a-documentation-for-checktags-and-tagtype-at.patch

@@ -24,7 +24,7 @@ index 1cd6f26fd93e06e9c2ba4176c64daa6cdaf0048a..11b9555628735dccb8db88e5a4ee3c41
 +@cindex @code{checktags} function attribute
 +The @code{checktags} tells the some parameters of the function are
 +taglists. In turn it will enable tag-type checking at compile-time, by
-+leveraging the extra information provded to enum-defined tags to which
++leveraging the extra information provided to enum-defined tags to which
 +a @code{tagtype} attribute is associated. The check assumes that if a
 +parameter is an integer constant to which a type is associated, then
 +it must be followed by an argument of that type. If that is not the

gcc/4.9/patches/0001-Changes-for-AmigaOS-version-of-gcc.patch

@@ -134,7 +134,7 @@ index 8856701850274bed70a9939e33640d12e015acd4..eee12b41f07bc3a046647e024e762f63
  			      handle_warn_unused_result_attribute, false },
 +  { "libcall",                0, 0, false, true,  true,
 +                              handle_libcall_attribute, false },
-+  /* Similiar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
++  /* Similar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
 +  { "libcall2",               0, 0, false, true,  true,
 +                              handle_libcall_attribute, false },
    { "sentinel",               0, 1, false, true, true,
@@ -1801,7 +1801,7 @@ index 94637f72187e6d8b49df2eb69b229323b3ccf9a3..c154af775ec4be18309397db30a00c86
 +;; generated instead of elf_base_low. Since the requirements for elf_base_low
 +;; are more restrictive than those for elf_low, there should be no problems
 +;; when determining which instruction to use. Additionally, the elf_low function
-+;; has now been guared against used accidently.
++;; has now been guarded against being used accidentally.
 +(define_insn "elf_base_high"
 +  [(set (match_operand:SI 0 "gpc_reg_operand" "=b")
 +        (plus:SI (match_operand:SI 1 "gpc_reg_operand" "b")

gcc/5/patches/0001-Changes-for-AmigaOS-version-of-gcc.patch

@@ -133,7 +133,7 @@ index 4d849fc19e88a80885cd3727fbfe48d6e9fe7a55..57c8cad50ae657fd173b6bbfa57d5adf
  			      handle_warn_unused_result_attribute, false },
 +  { "libcall",                0, 0, false, true,  true,
 +                              handle_libcall_attribute, false },
-+  /* Similiar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
++  /* Similar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
 +  { "libcall2",               0, 0, false, true,  true,
 +                              handle_libcall_attribute, false },
    { "sentinel",               0, 1, false, true, true,
@@ -1797,7 +1797,7 @@ index 6ab47268be5ab13f23b2a6da8d9aac2f01314662..cb643d2ccd3ec99b6e5ed81c12634afd
 +;; generated instead of elf_base_low. Since the requirements for elf_base_low
 +;; are more restrictive than those for elf_low, there should be no problems
 +;; when determining which instruction to use. Additionally, the elf_low function
-+;; has now been guared against used accidently.
++;; has now been guarded against being used accidentally.
 +(define_insn "elf_base_high"
 +  [(set (match_operand:SI 0 "gpc_reg_operand" "=b")
 +        (plus:SI (match_operand:SI 1 "gpc_reg_operand" "b")

gcc/5/patches/0007-Some-AmigaOS-4.x-compability-changes-for-posix-threa.patch

@@ -1,7 +1,7 @@
 From 8061772b6c3692fd8c7ae49780897027ec26cfeb Mon Sep 17 00:00:00 2001
 From: Sebastian Bauer <mail@sebastianbauer.info>
 Date: Thu, 21 Jan 2016 20:46:59 +0100
-Subject: [PATCH 07/13] Some AmigaOS 4.x compability changes for posix thread
+Subject: [PATCH 07/13] Some AmigaOS 4.x compatibility changes for posix thread
  support.
 
 ---

gcc/5/patches/0013-Avoid-section-anchors-in-the-baserel-mode.patch

@@ -38,7 +38,7 @@ index c5ef0eb02b63941c617530466a2f639b3cf9afbe..aa6dc11edd7db97484567859ce4083a4
 +
 +/* Addititionally to the normal anchor (optimization) suppression, suppress
 + * it also in the baserel mode because we don't adjust the anchor access yet.
-+ * It would make some sence to support anchros also in baserel mode, because
++ * It would make some sense to support anchors also in baserel mode, because
 + * baserel access is 32 bit.
 + */
 +bool

gcc/6/patches/0001-Changes-for-AmigaOS-version-of-gcc.patch

@@ -133,7 +133,7 @@ index 6cf8c610b4edc37e321db36c71163aaebadadb79..28478e431caa03d73634ad81c69f846f
  			      handle_warn_unused_result_attribute, false },
 +  { "libcall",                0, 0, false, true,  true,
 +                              handle_libcall_attribute, false },
-+  /* Similiar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
++  /* Similar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
 +  { "libcall2",               0, 0, false, true,  true,
 +                              handle_libcall_attribute, false },
    { "sentinel",               0, 1, false, true, true,
@@ -1805,7 +1805,7 @@ index 2ff61a23dd30cace5b67286d21ef5b63fd7d88c5..d3d3a7cb3900212ffb75828b6d1ba3dc
 +;; generated instead of elf_base_low. Since the requirements for elf_base_low
 +;; are more restrictive than those for elf_low, there should be no problems
 +;; when determining which instruction to use. Additionally, the elf_low function
-+;; has now been guared against used accidently.
++;; has now been guarded against being used accidentally.
 +(define_insn "elf_base_high"
 +  [(set (match_operand:SI 0 "gpc_reg_operand" "=b")
 +        (plus:SI (match_operand:SI 1 "gpc_reg_operand" "b")

gcc/6/patches/0007-Some-AmigaOS-4.x-compability-changes-for-posix-threa.patch

@@ -1,7 +1,7 @@
 From 35669b2c7f84f356af24dfbab6040214e22497c0 Mon Sep 17 00:00:00 2001
 From: Sebastian Bauer <mail@sebastianbauer.info>
 Date: Thu, 21 Jan 2016 20:46:59 +0100
-Subject: [PATCH 07/20] Some AmigaOS 4.x compability changes for posix thread
+Subject: [PATCH 07/20] Some AmigaOS 4.x compatibility changes for posix thread
  support.
 
 ---

gcc/6/patches/0017-Avoid-section-anchors-in-the-baserel-mode.patch

@@ -38,7 +38,7 @@ index 0749b33bab279bebf7146a7592c4fc02b69816d2..3a2588bab04f023eeb31b4244a297012
 +
 +/* Addititionally to the normal anchor (optimization) suppression, suppress
 + * it also in the baserel mode because we don't adjust the anchor access yet.
-+ * It would make some sence to support anchros also in baserel mode, because
++ * It would make some sense to support anchors also in baserel mode, because
 + * baserel access is 32 bit.
 + */
 +bool

gcc/8/patches/0001-Changes-for-AmigaOS-version-of-gcc.patch

@@ -133,7 +133,7 @@ index 61249cf94771ad0860b9fc8c582f4371fbc13c71..a3792f9bfae8022597391ff45e8c9ede
  	                      attr_warn_unused_result_exclusions },
 +  { "libcall",                0, 0, false, true, true, false,
 +                              handle_libcall_attribute, NULL },
-+  /* Similiar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
++  /* Similar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
 +  { "libcall2",               0, 0, false, true, true, false,
 +                              handle_libcall_attribute, NULL },
    { "sentinel",               0, 1, false, true, true, false,
@@ -1812,7 +1812,7 @@ index 4dbe8e5d133513f0e23affa2680c84f9aedf0a95..f086ad317ffeb21c5333574f07243ac8
 +;; generated instead of elf_base_low. Since the requirements for elf_base_low
 +;; are more restrictive than those for elf_low, there should be no problems
 +;; when determining which instruction to use. Additionally, the elf_low function
-+;; has now been guared against used accidently.
++;; has now been guarded against being used accidentally.
 +(define_insn "elf_base_high"
 +  [(set (match_operand:SI 0 "gpc_reg_operand" "=b")
 +        (plus:SI (match_operand:SI 1 "gpc_reg_operand" "b")

gcc/8/patches/0007-Some-AmigaOS-4.x-compability-changes-for-posix-threa.patch

@@ -1,7 +1,7 @@
 From 6c50d0f39edd65987c4bfb486e54e0f9498e3a3f Mon Sep 17 00:00:00 2001
 From: Sebastian Bauer <mail@sebastianbauer.info>
 Date: Thu, 21 Jan 2016 20:46:59 +0100
-Subject: [PATCH 07/29] Some AmigaOS 4.x compability changes for posix thread
+Subject: [PATCH 07/29] Some AmigaOS 4.x compatibility changes for posix thread
  support.
 
 ---

gcc/8/patches/0017-Avoid-section-anchors-in-the-baserel-mode.patch

@@ -38,7 +38,7 @@ index 85c03f28e37d64865360692a14fcc8a197b55395..a7cfaaa2ca4ac913d78e3240aa994a65
 +
 +/* Addititionally to the normal anchor (optimization) suppression, suppress
 + * it also in the baserel mode because we don't adjust the anchor access yet.
-+ * It would make some sence to support anchros also in baserel mode, because
++ * It would make some sense to support anchors also in baserel mode, because
 + * baserel access is 32 bit.
 + */
 +bool

gcc/8/patches/0020-Add-tagtype-attribute-that-can-be-passed-to-enum-con.patch

@@ -140,7 +140,7 @@ index a7cfaaa2ca4ac913d78e3240aa994a65c2e4b03f..db803847e90047b90c8c88e3aa9b50c8
 +
  /* Addititionally to the normal anchor (optimization) suppression, suppress
   * it also in the baserel mode because we don't adjust the anchor access yet.
-  * It would make some sence to support anchros also in baserel mode, because
+  * It would make some sense to support anchors also in baserel mode, because
   * baserel access is 32 bit.
   */
  bool

gcc/8/patches/0023-Provide-a-documentation-for-checktags-and-tagtype-at.patch

@@ -24,7 +24,7 @@ index 74e4196842260a7904a71279ad08f311660c4527..cb1b4aafd131f08f7ec4641ddfdb7687
 +@cindex @code{checktags} function attribute
 +The @code{checktags} tells the some parameters of the function are
 +taglists. In turn it will enable tag-type checking at compile-time, by
-+leveraging the extra information provded to enum-defined tags to which
++leveraging the extra information provided to enum-defined tags to which
 +a @code{tagtype} attribute is associated. The check assumes that if a
 +parameter is an integer constant to which a type is associated, then
 +it must be followed by an argument of that type. If that is not the

gcc/9/patches/0001-Changes-for-AmigaOS-version-of-gcc.patch

@@ -133,7 +133,7 @@ index 93b210eed9ca004a7f9b7fc3e24134bd5c04957a..2b33a0649764196b555d46a5b189ddea
  	                      attr_warn_unused_result_exclusions },
 +  { "libcall",                0, 0, false, true, true, false,
 +                              handle_libcall_attribute, NULL },
-+  /* Similiar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
++  /* Similar to libcall but doesn't imply linearvarargs. Can be handled as libcall here. */
 +  { "libcall2",               0, 0, false, true, true, false,
 +                              handle_libcall_attribute, NULL },
    { "sentinel",               0, 1, false, true, true, false,
@@ -1812,7 +1812,7 @@ index ad80592765d047db68d61e64bb48a7ec0cf48ddd..4861ba44e108c5c2ef1f42850738ce7a
 +;; generated instead of elf_base_low. Since the requirements for elf_base_low
 +;; are more restrictive than those for elf_low, there should be no problems
 +;; when determining which instruction to use. Additionally, the elf_low function
-+;; has now been guared against used accidently.
++;; has now been guarded against being used accidentally.
 +(define_insn "elf_base_high"
 +  [(set (match_operand:SI 0 "gpc_reg_operand" "=b")
 +        (plus:SI (match_operand:SI 1 "gpc_reg_operand" "b")

gcc/9/patches/0007-Some-AmigaOS-4.x-compability-changes-for-posix-threa.patch

@@ -1,7 +1,7 @@
 From 8ba761c3761a87cdf6a5ece5b7fa5c225e001003 Mon Sep 17 00:00:00 2001
 From: Sebastian Bauer <mail@sebastianbauer.info>
 Date: Thu, 21 Jan 2016 20:46:59 +0100
-Subject: [PATCH 07/32] Some AmigaOS 4.x compability changes for posix thread
+Subject: [PATCH 07/32] Some AmigaOS 4.x compatibility changes for posix thread
  support.
 
 ---

gcc/9/patches/0017-Avoid-section-anchors-in-the-baserel-mode.patch

@@ -38,7 +38,7 @@ index 85c03f28e37d64865360692a14fcc8a197b55395..a7cfaaa2ca4ac913d78e3240aa994a65
 +
 +/* Addititionally to the normal anchor (optimization) suppression, suppress
 + * it also in the baserel mode because we don't adjust the anchor access yet.
-+ * It would make some sence to support anchros also in baserel mode, because
++ * It would make some sense to support anchors also in baserel mode, because
 + * baserel access is 32 bit.
 + */
 +bool