Search Options

Results per page
Sort
Preferred Languages
Advance

Results 121 - 130 of 172 for syntaxe (0.14 sec)

  1. src/main/java/jcifs/smb1/dcerpc/msrpc/lsarpc.java

        /**
         * Private constructor to prevent instantiation of utility class.
         */
        private lsarpc() {
            // Utility class
        }
    
        /**
         * Returns the RPC syntax identifier for LSA RPC interface.
         *
         * @return the RPC syntax string
         */
        public static String getSyntax() {
            return "12345778-1234-abcd-ef00-0123456789ab:0.0";
        }
    
        /**
         * LSA Quality of Service information.
    Registered: Sun Sep 07 00:10:21 UTC 2025
    - Last Modified: Sat Aug 16 01:32:48 UTC 2025
    - 42.5K bytes
    - Viewed (0)
  2. src/main/java/org/codelibs/core/convert/TimeConversionUtil.java

     * </tr>
     * <tr>
     * <td>{@link DateFormat#FULL} format without delimiters</td>
     * <td>{@literal HHmmss z}</td>
     * </tr>
     * <tr>
     * <td>Other</td>
     * <td>{@link Time#valueOf(String) JDBC escape syntax} format</td>
     * <td>{@literal HH:mm:ss}</td>
     * </tr>
     * </table>
     *
     * @author koichik
     * @see DateConversionUtil
     * @see TimestampConversionUtil
     */
    public abstract class TimeConversionUtil {
    
    Registered: Fri Sep 05 20:58:11 UTC 2025
    - Last Modified: Thu Jul 31 08:16:49 UTC 2025
    - 20.3K bytes
    - Viewed (0)
  3. docs/de/docs/tutorial/response-model.md

    Das trifft auch auf `response_model_by_alias` zu, welches ähnlich funktioniert.
    
    ///
    
    {* ../../docs_src/response_model/tutorial005_py310.py hl[29,35] *}
    
    /// tip | Tipp
    
    Die Syntax `{"name", "description"}` erzeugt ein `set` mit diesen zwei Werten.
    
    Äquivalent zu `set(["name", "description"])`.
    
    ///
    
    #### `list`en statt `set`s verwenden
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Mon Nov 18 02:25:44 UTC 2024
    - 16.9K bytes
    - Viewed (0)
  4. src/main/java/org/codelibs/fess/taglib/FessFunctions.java

            if (input == null) {
                return StringUtil.EMPTY;
            }
            return input.toString().replaceAll(regex, replacement);
        }
    
        /**
         * Formats code content with syntax highlighting and line numbers.
         *
         * @param prefix the line number prefix pattern
         * @param style the CSS class name for styling
         * @param mimetype the MIME type of the content (currently unused)
    Registered: Thu Sep 04 12:52:25 UTC 2025
    - Last Modified: Thu Aug 07 03:06:29 UTC 2025
    - 25.3K bytes
    - Viewed (1)
  5. okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/-HostnamesCommon.kt

      for (i in 0 until length) {
        val c = this[i]
        // The WHATWG Host parsing rules accepts some character codes which are invalid by
        // definition for OkHttp's host header checks (and the WHATWG Host syntax definition). Here
        // we rule out characters that would cause problems in host headers.
        if (c <= '\u001f' || c >= '\u007f') {
          return true
        }
    Registered: Fri Sep 05 11:42:10 UTC 2025
    - Last Modified: Wed Mar 19 19:25:20 UTC 2025
    - 11.2K bytes
    - Viewed (0)
  6. LICENSE

          boilerplate notice, with the fields enclosed by brackets "{}"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Thu Sep 04 15:34:10 UTC 2025
    - Last Modified: Thu Jun 14 07:45:22 UTC 2018
    - 11.1K bytes
    - Viewed (0)
  7. LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Tue Nov 22 19:44:46 UTC 2016
    - 11.1K bytes
    - Viewed (0)
  8. LICENSES/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.3K bytes
    - Viewed (0)
  9. LICENSES/vendor/github.com/NYTimes/gziphandler/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Feb 03 21:57:36 UTC 2021
    - 11.2K bytes
    - Viewed (0)
  10. LICENSES/vendor/github.com/container-storage-interface/spec/LICENSE

          boilerplate notice, with the fields enclosed by brackets "{}"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.3K bytes
    - Viewed (0)
Back to top