@chilkat/react-native 11.6.1

package/src/specs/Dh.nitro.ts

@@ -0,0 +1,343 @@
+// Generated by ReactNativeNs.RnGenerator -- do not edit.
+import type { HybridObject } from 'react-native-nitro-modules'
+
+/**
+ * Perform Diffie-Hellman shared-secret key exchange.
+ *
+ * `Dh` provides the core operations needed for
+ * Diffie-Hellman shared-secret exchange. It allows two parties to agree on a
+ * shared secret over an insecure channel by using common Diffie-Hellman
+ * parameters, generating public exchange values, and computing the same shared
+ * secret from the other party's public value.
+ *
+ * **Choose known parameters**
+ *
+ * Use `UseKnownPrime` when the application wants to use a
+ * predefined Diffie-Hellman prime group.
+ *
+ * **Generate parameters**
+ *
+ * Use `GenPG` to generate Diffie-Hellman parameters when custom
+ * prime and generator values are required.
+ *
+ * **Set custom P and G**
+ *
+ * Use `SetPG` when the prime and generator are already known or
+ * have been received from another party or protocol.
+ *
+ * **Create the exchange value**
+ *
+ * Use `CreateE` to create the public Diffie-Hellman value that
+ * is sent to the other party.
+ *
+ * **Compute the shared secret**
+ *
+ * Use `FindK` with the other party's public exchange value to
+ * compute the shared secret.
+ *
+ * **Use the result carefully**
+ *
+ * The shared secret is typically used as input to a key derivation step
+ * before being used for encryption or authentication.
+ *
+ * **Common pattern:**
+ * Select or generate the Diffie-Hellman parameters, create your public
+ * exchange value with `CreateE`, exchange public values with the
+ * other party, then call `FindK` to compute the shared secret. The
+ * primary methods are `UseKnownPrime`, `GenPG`,
+ * `SetPG`, `CreateE`, and `FindK`.
+ *
+ * For an extended overview, see
+ * [Dh Class Overview](https://www.chilkatsoft.com/dh_class_overview.asp).
+ *
+ * Each `Dh` instance owns a native Chilkat object. It is released when the JavaScript object is
+ * garbage collected, or immediately by `dispose()`; any use after `dispose()` throws.
+ * Create one with `new Dh()`.
+ */
+export interface Dh extends HybridObject<{ ios: 'c++', android: 'c++' }> {
+  // ---- Properties ----
+
+  /**
+   * Provides HTML-formatted information about the last called method or property. If a method call
+   * fails or behaves unexpectedly, check this property for details. Note that information is
+   * available regardless of the method call's success.
+   *
+   * This property is read-only.
+   */
+  readonly lastErrorHtml: string
+
+  /**
+   * Provides plain text information about the last called method or property. If a method call
+   * fails or behaves unexpectedly, check this property for details. Note that information is
+   * available regardless of the method call's success.
+   *
+   * This property is read-only.
+   */
+  readonly lastErrorText: string
+
+  /**
+   * Provides XML-formatted information about the last called method or property. If a method call
+   * fails or behaves unexpectedly, check this property for details. Note that information is
+   * available regardless of the method call's success.
+   *
+   * This property is read-only.
+   */
+  readonly lastErrorXml: string
+
+  /**
+   * Version of the component/library, such as "10.1.0"
+   *
+   * This property is read-only.
+   */
+  readonly version: string
+
+  /**
+   * If set to a file path, this property logs the LastErrorText of each Chilkat method or property
+   * call to the specified file. This logging helps identify the context and history of Chilkat
+   * calls leading up to any crash or hang, aiding in debugging.
+   *
+   * Enabling the VerboseLogging property provides more detailed information.
+   *
+   * This property is mainly used for debugging rare instances where a Chilkat method call causes a
+   * hang or crash, which should generally not happen.
+   *
+   * Possible causes of hangs include:
+   *
+   * - A timeout property set to 0, indicating an infinite timeout.
+   *
+   * - A hang occurring within an event callback in the application code.
+   *
+   * - An internal bug in the Chilkat code causing the hang.
+   */
+  debugLogFilePath: string
+
+  /**
+   * If set to `true`, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may
+   * contain more verbose information. The default value is `false`. Verbose logging should only be
+   * used for debugging. The potentially large quantity of logged information may adversely affect
+   * peformance.
+   */
+  verboseLogging: boolean
+
+  /**
+   * Indicates the success or failure of the most recent method call: `true` means success, `false`
+   * means failure. This property remains unchanged by property setters or getters. This method is
+   * present to address challenges in checking for null or Nothing returns in certain programming
+   * languages. Note: This property does not apply to methods that return integer values or to
+   * boolean-returning methods where the boolean does not indicate success or failure.
+   */
+  lastMethodSuccess: boolean
+
+  /**
+   * Returns the current Diffie-Hellman generator, `g`. The generator is the
+   * small public integer used with the prime modulus `p` in the modular
+   * exponentiation operations that create the public exchange value and shared secret.
+   *
+   * For this class, `g` is expected to be `2` or `5`.
+   * Its value is established by `UseKnownPrime`, `GenPG`, or
+   * `SetPG`.
+   *
+   * **Public parameter:**
+   * The generator is not secret. Both parties must use exactly the same
+   * `p` and `g` values for the exchange.
+   *
+   * This property is read-only.
+   */
+  readonly g: number
+
+  /**
+   * Returns the current Diffie-Hellman prime modulus, `p`, as a
+   * hex-encoded SSH1-format bignum. The value is established by
+   * `UseKnownPrime`, `GenPG`, or `SetPG`.
+   *
+   * The modulus is a \*safe prime\*: `p = 2q + 1`, where
+   * `q` is also prime. Safe-prime groups are commonly used for
+   * finite-field Diffie-Hellman because their subgroup structure is well understood.
+   *
+   * **Encoding note:**
+   * The returned string is the hexadecimal encoding of an SSH1 bignum, which
+   * includes the SSH1 bit-length prefix. It is not simply the conventional
+   * hexadecimal representation of the integer `p`.
+   *
+   * **Public parameter:**
+   * The prime modulus is not secret and may be transmitted to the other party.
+   * Both parties must use the same `p` and `g`.
+   *
+   * This property is read-only.
+   */
+  readonly p: string
+
+  // ---- Methods ----
+
+  /**
+   * Creates this party's public Diffie-Hellman exchange value, conventionally written
+   * as `E = gx mod p`. Before calling this method, initialize
+   * the common Diffie-Hellman parameters by calling `UseKnownPrime`,
+   * `GenPG`, or `SetPG`.
+   *
+   * `ARG1` (`numBits`) controls the size of the randomly
+   * generated private exponent retained internally by this `Dh` object.
+   * Chilkat recommends setting it to twice the desired strength of the symmetric key
+   * that will ultimately be derived. For example, use `256` when the
+   * protocol will derive a 128-bit key.
+   *
+   * The returned `E` value is a hex-encoded SSH1-format bignum. It is
+   * public and is sent to the other party. The size of the eventual shared-secret
+   * integer is determined primarily by `p`; `numBits` does
+   * not make the returned shared secret a fixed-length symmetric key.
+   *
+   * **Object state:**
+   * Call `FindK` on this same `Dh` object after receiving the
+   * other party's exchange value. `CreateE` stores the corresponding
+   * private value internally, and `FindK` needs it to compute the shared
+   * secret. Use a separate `Dh` object for each party and generate a
+   * fresh exchange value for each session.
+   *
+   * **Authentication required:**
+   * Basic Diffie-Hellman does not authenticate either party and is vulnerable to a
+   * man-in-the-middle attack. The surrounding protocol must authenticate the
+   * exchanged parameters and public values.
+   *
+   * For language bindings where a string return cannot directly communicate failure,
+   * check `LastMethodSuccess`. If it is `FALSE`, inspect
+   * `LastErrorText`.
+   *
+   * @throws Error if the call fails (the message names the reason); the full log is in
+   * {@link Dh.lastErrorText}.
+   */
+  createE(numBits: number): string
+
+  /**
+   * Computes the Diffie-Hellman shared secret from the other party's public exchange
+   * value. `ARG1` is the peer's `E` value, encoded as the
+   * hexadecimal representation of an SSH1-format bignum.
+   *
+   * This method must be called on the same `Dh` object that previously
+   * called `CreateE`. Both parties must also be using the same
+   * `p` and `g` parameters. Internally, the method computes
+   * `K = Ex mod p`, where `x` is the private value
+   * generated by `CreateE`.
+   *
+   * The result is the shared-secret integer `K`, returned as a
+   * hex-encoded SSH1-format bignum. When the exchange is performed correctly, both
+   * parties compute the same value.
+   *
+   * **Do not use the returned text directly as an encryption key:**
+   * It is an encoded bignum, not a uniformly formatted symmetric key. Feed the
+   * shared-secret value into the key-derivation procedure required by the protocol,
+   * together with any required transcript, salt, labels, or context. Do not invent
+   * an ad hoc conversion when interoperability or cryptographic security matters.
+   *
+   * **Key agreement is not authentication:**
+   * Matching shared secrets do not by themselves prove the identity of the peer.
+   * Authenticate the exchange to prevent man-in-the-middle attacks.
+   *
+   * For language bindings where a string return cannot directly communicate failure,
+   * check `LastMethodSuccess`. If it is `FALSE`, inspect
+   * `LastErrorText`.
+   *
+   * @throws Error if the call fails (the message names the reason); the full log is in
+   * {@link Dh.lastErrorText}.
+   */
+  findK(e: string): string
+
+  /**
+   * Generates new finite-field Diffie-Hellman parameters and stores them in this
+   * object. `ARG1` specifies the size of the safe prime `p` in
+   * bits, and `ARG2` specifies the generator `g`, which should
+   * be `2` or `5`.
+   *
+   * On success, the generated values are available through the `P` and
+   * `G` properties. The prime generation and validation process is
+   * computationally expensive, especially for large groups.
+   *
+   * **Prefer standardized groups:**
+   * Most applications should use `UseKnownPrime` or parameters mandated
+   * by the surrounding protocol instead of generating a new group. Standardized
+   * groups improve interoperability and avoid the cost and risk of custom parameter
+   * generation.
+   *
+   * **Modern key sizes:**
+   * The legacy 768-, 1024-, and 1536-bit MODP groups are not appropriate for new
+   * designs. Use at least a 2048-bit standardized group when compatibility requires
+   * finite-field DH; a 3072-bit group is commonly selected when approximately
+   * 128-bit classical security is required.
+   *
+   * Returns `TRUE` if the parameters were generated successfully;
+   * otherwise returns `FALSE`. Check `LastErrorText` for
+   * failure details.
+   *
+   * @throws Error if the call fails (the message names the reason); the full log is in
+   * {@link Dh.lastErrorText}.
+   */
+  genPG(numBits: number, g: number): void
+
+  /**
+   * Sets explicit finite-field Diffie-Hellman parameters for this object.
+   * `ARG1` is the prime modulus `p`, supplied as a
+   * hex-encoded SSH1-format bignum, and `ARG2` is the generator
+   * `g`, normally `2` or `5`.
+   *
+   * The method validates that the supplied values satisfy the requirements expected
+   * by this Diffie-Hellman implementation. It returns `TRUE` if the
+   * parameters are accepted; otherwise it returns `FALSE`.
+   *
+   * **Encoding requirement:**
+   * `p` is not ordinary integer hex. It must contain the hexadecimal
+   * encoding of the SSH1 bignum representation, including its bit-length prefix.
+   * The `P` property of another Chilkat `Dh` object is
+   * already in the required form.
+   *
+   * **Interoperability:**
+   * Both parties must use exactly the same `p` and `g`.
+   * These values are public, but untrusted or nonstandard parameters should not be
+   * accepted unless the protocol explicitly permits them and their origin is
+   * authenticated.
+   *
+   * @throws Error if the call fails (the message names the reason); the full log is in
+   * {@link Dh.lastErrorText}.
+   */
+  setPG(p: string, g: number): void
+
+  /**
+   * Selects one of eight built-in safe-prime MODP groups and sets the object's
+   * `P` and `G` properties. `ARG1` is a Chilkat
+   * selector from `1` through `8`; it is **not**
+   * the IKE group number.
+   *
+   * `index`
+   * MODP group
+   * Prime bits
+   * Definition
+   * G
+   *
+   * | `1` |  | Group 1 |  | 768 |  | RFC 2409, section 6.1 |  | `2` |
+   *
+   * | `2` |  | Group 2 |  | 1024 |  | RFC 2409, section 6.2 |  | `2` |
+   *
+   * | `3` |  | Group 5 |  | 1536 |  | RFC 3526, section 2 |  | `2` |
+   *
+   * | `4` |  | Group 14 |  | 2048 |  | RFC 3526, section 3 |  | `2` |
+   *
+   * | `5` |  | Group 15 |  | 3072 |  | RFC 3526, section 4 |  | `2` |
+   *
+   * | `6` |  | Group 16 |  | 4096 |  | RFC 3526, section 5 |  | `2` |
+   *
+   * | `7` |  | Group 17 |  | 6144 |  | RFC 3526, section 6 |  | `2` |
+   *
+   * | `8` |  | Group 18 |  | 8192 |  | RFC 3526, section 7 |  | `2` |
+   *
+   * **Security guidance:**
+   * Selectors `1`, `2`, and `3` are legacy groups
+   * and should not be chosen for new systems. Selector `4` is the
+   * 2048-bit group 14; selector `5` is the 3072-bit group 15 and is
+   * commonly used when approximately 128-bit classical security is required.
+   * Always use the group required by the protocol or the communicating peer.
+   *
+   * **Performance:**
+   * Larger groups require more CPU time and produce larger public values. Choose a
+   * group based on the required security level and interoperability requirements,
+   * rather than automatically selecting the largest group.
+   */
+  useKnownPrime(index: number): void
+}

package/src/specs/DirTree.nitro.ts

@@ -0,0 +1,332 @@
+// Generated by ReactNativeNs.RnGenerator -- do not edit.
+import type { HybridObject } from 'react-native-nitro-modules'
+
+/**
+ * Iterate through files and subdirectories under a base directory.
+ *
+ * `DirTree` is a lightweight directory-tree iterator for
+ * traversing files and subdirectories under a selected base directory. It
+ * supports recursive and non-recursive traversal and exposes useful information
+ * about the current item, including absolute path, UNC path, relative path,
+ * file size, and whether the current item is a directory.
+ *
+ * **Directory traversal**
+ *
+ * Iterate through the contents of a base directory, either recursively or
+ * one level at a time.
+ *
+ * **Current-item details**
+ *
+ * Get the current item's full path, relative path, UNC path, size, and
+ * directory/file status.
+ *
+ * **Recursive scanning**
+ *
+ * Traverse entire directory trees when an application needs to process all
+ * nested files and folders.
+ *
+ * **Non-recursive listing**
+ *
+ * Limit iteration to the immediate contents of the base directory when
+ * deeper traversal is not needed.
+ *
+ * **Path-friendly output**
+ *
+ * Use absolute or relative paths depending on whether the application needs
+ * filesystem access or archive-style relative names.
+ *
+ * **Error-aware iteration**
+ *
+ * Use `DoneIterating` to distinguish normal completion from an
+ * error when an iteration method returns false.
+ *
+ * **Common pattern:**
+ * Set the base directory and recursion behavior, begin iterating, process each
+ * current item using the path and metadata properties, then check
+ * `DoneIterating` when iteration stops to determine whether traversal
+ * completed normally or ended because of an error.
+ *
+ * For an extended overview, see
+ * [DirTree Class Overview](https://www.chilkatsoft.com/dirtree_class_overview.asp).
+ *
+ * Each `DirTree` instance owns a native Chilkat object. It is released when the JavaScript object
+ * is
+ * garbage collected, or immediately by `dispose()`; any use after `dispose()` throws.
+ * Create one with `new DirTree()`.
+ */
+export interface DirTree extends HybridObject<{ ios: 'c++', android: 'c++' }> {
+  // ---- Properties ----
+
+  /**
+   * Provides HTML-formatted information about the last called method or property. If a method call
+   * fails or behaves unexpectedly, check this property for details. Note that information is
+   * available regardless of the method call's success.
+   *
+   * This property is read-only.
+   */
+  readonly lastErrorHtml: string
+
+  /**
+   * Provides plain text information about the last called method or property. If a method call
+   * fails or behaves unexpectedly, check this property for details. Note that information is
+   * available regardless of the method call's success.
+   *
+   * This property is read-only.
+   */
+  readonly lastErrorText: string
+
+  /**
+   * Provides XML-formatted information about the last called method or property. If a method call
+   * fails or behaves unexpectedly, check this property for details. Note that information is
+   * available regardless of the method call's success.
+   *
+   * This property is read-only.
+   */
+  readonly lastErrorXml: string
+
+  /**
+   * Version of the component/library, such as "10.1.0"
+   *
+   * This property is read-only.
+   */
+  readonly version: string
+
+  /**
+   * If set to a file path, this property logs the LastErrorText of each Chilkat method or property
+   * call to the specified file. This logging helps identify the context and history of Chilkat
+   * calls leading up to any crash or hang, aiding in debugging.
+   *
+   * Enabling the VerboseLogging property provides more detailed information.
+   *
+   * This property is mainly used for debugging rare instances where a Chilkat method call causes a
+   * hang or crash, which should generally not happen.
+   *
+   * Possible causes of hangs include:
+   *
+   * - A timeout property set to 0, indicating an infinite timeout.
+   *
+   * - A hang occurring within an event callback in the application code.
+   *
+   * - An internal bug in the Chilkat code causing the hang.
+   */
+  debugLogFilePath: string
+
+  /**
+   * If set to `true`, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may
+   * contain more verbose information. The default value is `false`. Verbose logging should only be
+   * used for debugging. The potentially large quantity of logged information may adversely affect
+   * peformance.
+   */
+  verboseLogging: boolean
+
+  /**
+   * Indicates the success or failure of the most recent method call: `true` means success, `false`
+   * means failure. This property remains unchanged by property setters or getters. This method is
+   * present to address challenges in checking for null or Nothing returns in certain programming
+   * languages. Note: This property does not apply to methods that return integer values or to
+   * boolean-returning methods where the boolean does not indicate success or failure.
+   */
+  lastMethodSuccess: boolean
+
+  /**
+   * Specifies the root directory whose contents are traversed. Set this property before calling
+   * `BeginIterate`.
+   *
+   * The value may be an absolute filesystem path or a relative path. A relative path is resolved
+   * from the calling process's current working directory.
+   *
+   * **Iteration scope:** The iterator visits the files and subdirectories contained under this
+   * directory. The `Recurse` property determines whether nested levels are included.
+   */
+  baseDir: string
+
+  /**
+   * Indicates whether the traversal has reached its normal end and no current item remains.
+   *
+   * This property is especially important because both `BeginIterate` and `AdvancePosition` can
+   * return \*`false`\* for either normal completion or an error:
+   *
+   * Method result
+   * `DoneIterating`
+   * Meaning
+   *
+   * | `false` |
+   * | `true` |
+   * | The directory was empty, or the last item has been passed. This is normal completion. |
+   *
+   * | `false` |
+   * | `false` |
+   * | An error occurred. Examine `LastErrorText`. |
+   *
+   * This property is read-only.
+   */
+  readonly doneIterating: boolean
+
+  /**
+   * Returns the size of the current file in bytes as a 32-bit integer. The value is `0` when the
+   * current item is a directory.
+   *
+   * **Large files:** A 32-bit integer cannot represent all modern file sizes. Use `FileSize64` when
+   * the language binding provides it, or `FileSizeStr` when a decimal string is more portable.
+   *
+   * This property is read-only.
+   */
+  readonly fileSize32: number
+
+  /**
+   * Returns the size of the current file in bytes as a 64-bit integer. The value is `0` when the
+   * current item is a directory.
+   *
+   * This is the preferred numeric size property for files that may exceed the range of
+   * `FileSize32`. In bindings that do not expose a 64-bit integer property, use `FileSizeStr`.
+   *
+   * This property is read-only.
+   *
+   * A 64-bit integer in Chilkat; JavaScript numbers are exact up to 2^53.
+   */
+  readonly fileSize64: number
+
+  /**
+   * Returns the absolute filesystem path of the current file or subdirectory, including the item's
+   * name.
+   *
+   * The path uses the native path syntax for the operating system. For a path relative to
+   * `BaseDir`, use `RelativePath`.
+   *
+   * This property is read-only.
+   */
+  readonly fullPath: string
+
+  /**
+   * Returns the current item's Windows extended-length absolute path. For example, a local path may
+   * be returned as `\\?\C:\data\reports\file.txt`; a network path may use the
+   * `\\?\UNC\server\share\...` form.
+   *
+   * **Windows path form:** The `\\?\` prefix asks Windows to use extended-length path parsing and
+   * is useful when working with paths that may exceed legacy path-length limits. Use `FullPath`
+   * when an ordinary native absolute path is preferred.
+   *
+   * This property is read-only.
+   */
+  readonly fullUncPath: string
+
+  /**
+   * Returns \*`true`\* when the current item is a subdirectory and \*`false`\* when it is a file.
+   *
+   * Check this property before using a file-size property. Directory items report a size of `0`.
+   *
+   * This property is read-only.
+   */
+  readonly isDirectory: boolean
+
+  /**
+   * Controls whether traversal descends into nested subdirectories.
+   *
+   * `true`
+   * | Visit files and directories throughout the complete tree rooted at `BaseDir`. |
+   *
+   * `false`
+   * | Visit only the immediate contents of `BaseDir`. |
+   *
+   * The default value is \*`true`\*. Set this property before calling `BeginIterate`.
+   */
+  recurse: boolean
+
+  /**
+   * Returns the path of the current file or subdirectory relative to `BaseDir`, including the
+   * item's name.
+   *
+   * For example, if `BaseDir` is `C:\data` and the current item is `C:\data\images\logo.png`, this
+   * property returns `images\logo.png` on Windows. Path separators follow the operating system's
+   * native convention.
+   *
+   * This property is read-only.
+   */
+  readonly relativePath: string
+
+  /**
+   * Returns the size of the current file in bytes as an unsigned decimal string. The value is `0`
+   * when the current item is a directory.
+   *
+   * This representation is useful for very large files and for language bindings where a 64-bit
+   * integer is unavailable or inconvenient. Convert the string to an appropriate
+   * arbitrary-precision or 64-bit numeric type only when arithmetic is required.
+   *
+   * This property is read-only.
+   */
+  readonly fileSizeStr: string
+
+  /**
+   * Provides a comma-separated list of specialized compatibility options. The default is the empty
+   * string, and applications should normally leave it unchanged.
+   *
+   * Keyword
+   * Effect
+   *
+   * | `Q_EncodePaths` |
+   * | Returns path-valued output properties in Chilkat's Q-encoded representation. Introduced in
+   * Chilkat v11.1.0. This changes only the returned string representation; it does not change which
+   * filesystem items are traversed. |
+   */
+  uncommonOptions: string
+
+  // ---- Methods ----
+
+  /**
+   * Advances the traversal from the current item to the next file or subdirectory.
+   *
+   * If the method returns \*`true`\*, the current-item properties—such as `FullPath`,
+   * `RelativePath`, `IsDirectory`, and the file-size properties—describe the newly selected item.
+   *
+   * Return value
+   * `DoneIterating`
+   * Meaning
+   *
+   * | `true` |
+   * | `false` |
+   * | The iterator advanced successfully and a current item is available. |
+   *
+   * | `false` |
+   * | `true` |
+   * | The last item has been passed; traversal completed normally. |
+   *
+   * | `false` |
+   * | `false` |
+   * | An error occurred. Examine `LastErrorText`. |
+   *
+   * @throws Error if the call fails (the message names the reason); the full log is in
+   * {@link DirTree.lastErrorText}.
+   */
+  advancePosition(): void
+
+  /**
+   * Initializes a new traversal using the current `BaseDir` and `Recurse` settings.
+   *
+   * If the method returns \*`true`\*, the iterator is positioned at the first file or subdirectory,
+   * and the current-item properties can be read immediately. Continue by processing that item and
+   * then calling `AdvancePosition`.
+   *
+   * Return value
+   * `DoneIterating`
+   * Meaning
+   *
+   * | `true` |
+   * | `false` |
+   * | The first item is available. |
+   *
+   * | `false` |
+   * | `true` |
+   * | The directory contains no items in the selected traversal scope. This is not an error. |
+   *
+   * | `false` |
+   * | `false` |
+   * | Initialization failed. Examine `LastErrorText`. |
+   *
+   * **Property lifetime:** Treat the current-item properties as valid only while the iterator is
+   * positioned on an item—that is, after a successful `BeginIterate` or `AdvancePosition`.
+   *
+   * @throws Error if the call fails (the message names the reason); the full log is in
+   * {@link DirTree.lastErrorText}.
+   */
+  beginIterate(): void
+}