Search Options

Results per page
Sort
Preferred Languages
Advance

Results 111 - 120 of 218 for syntax (0.14 sec)

  1. src/main/java/org/codelibs/core/convert/DateConversionUtil.java

     * </tr>
     * <tr>
     * <td>{@link DateFormat#FULL} format without delimiters</td>
     * <td>{@literal yyyyMMdd}</td>
     * </tr>
     * <tr>
     * <td>Other</td>
     * <td>{@link java.sql.Date#valueOf(String) Jdbc escape syntax} format</td>
     * <td>{@literal yyyy-MM-dd}</td>
     * </tr>
     * </table>
     *
     * @author higa
     * @see TimeConversionUtil
     * @see TimestampConversionUtil
     */
    public abstract class DateConversionUtil {
    
    Registered: Fri Sep 05 20:58:11 UTC 2025
    - Last Modified: Thu Jul 31 08:16:49 UTC 2025
    - 19.6K bytes
    - Viewed (0)
  2. src/main/java/jcifs/smb1/dcerpc/msrpc/srvsvc.java

     */
    public class srvsvc {
    
        /**
         * Private constructor to prevent instantiation.
         */
        private srvsvc() {
        }
    
        /**
         * Gets the RPC interface syntax string.
         * @return the interface UUID and version
         */
        public static String getSyntax() {
            return "4b324fc8-1670-01d3-1278-5a47bf6ee188:3.0";
        }
    
        /**
    Registered: Sun Sep 07 00:10:21 UTC 2025
    - Last Modified: Sat Aug 16 01:32:48 UTC 2025
    - 26.3K bytes
    - Viewed (0)
  3. api/go1.txt

    pkg regexp/syntax, const InstMatch InstOp
    pkg regexp/syntax, const InstNop InstOp
    pkg regexp/syntax, const InstRune InstOp
    pkg regexp/syntax, const InstRune1 InstOp
    pkg regexp/syntax, const InstRuneAny InstOp
    pkg regexp/syntax, const InstRuneAnyNotNL InstOp
    pkg regexp/syntax, const Literal Flags
    pkg regexp/syntax, const MatchNL Flags
    pkg regexp/syntax, const NonGreedy Flags
    Registered: Tue Sep 09 11:13:09 UTC 2025
    - Last Modified: Wed Aug 14 18:58:28 UTC 2013
    - 1.7M bytes
    - Viewed (0)
  4. 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 12:52:25 UTC 2025
    - Last Modified: Tue May 08 21:35:34 UTC 2018
    - 11.1K bytes
    - Viewed (0)
  5. LICENSES/vendor/github.com/euank/go-kmsg-parser/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.2K bytes
    - Viewed (0)
  6. LICENSES/vendor/github.com/go-logr/zapr/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: Thu Sep 09 12:43:43 UTC 2021
    - 11.2K bytes
    - Viewed (0)
  7. LICENSES/vendor/github.com/go-openapi/jsonpointer/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.2K bytes
    - Viewed (0)
  8. LICENSES/vendor/github.com/go-openapi/jsonreference/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.2K bytes
    - Viewed (0)
  9. LICENSES/vendor/github.com/go-openapi/swag/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.2K bytes
    - Viewed (0)
  10. 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 19 09:08:11 UTC 2025
    - Last Modified: Mon Jan 11 04:30:09 UTC 2021
    - 11.1K bytes
    - Viewed (0)
Back to top