- Sort Score
- Num 10 results
- Language All
Results 151 - 160 of 204 for syntaxe (0.07 seconds)
-
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.
Created: Fri Dec 26 09:05:12 GMT 2025 - Last Modified: Tue Nov 22 19:44:46 GMT 2016 - 11.1K bytes - Click Count (0) -
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.
Created: Fri Dec 26 09:05:12 GMT 2025 - Last Modified: Fri May 08 04:49:00 GMT 2020 - 11.3K bytes - Click Count (0) -
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.
Created: Fri Dec 26 09:05:12 GMT 2025 - Last Modified: Wed Feb 03 21:57:36 GMT 2021 - 11.2K bytes - Click Count (0) -
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.
Created: Fri Dec 26 09:05:12 GMT 2025 - Last Modified: Fri May 08 04:49:00 GMT 2020 - 11.3K bytes - Click Count (0) -
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.
Created: Sat Dec 20 08:55:33 GMT 2025 - Last Modified: Fri Apr 18 13:54:00 GMT 2025 - 11.1K bytes - Click Count (0) -
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.
Created: Sat Dec 20 09:13:53 GMT 2025 - Last Modified: Thu Jun 14 07:45:22 GMT 2018 - 11.1K bytes - Click Count (0) -
apache-maven/src/main/appended-resources/licenses/Apache-2.0.txt
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.
Created: Sun Dec 28 03:35:09 GMT 2025 - Last Modified: Tue Jan 28 11:47:17 GMT 2020 - 11.1K bytes - Click Count (0) -
CREDITS
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.
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Thu Mar 13 05:29:51 GMT 2025 - 1.8M bytes - Click Count (0) -
src/main/java/jcifs/dcerpc/msrpc/samr.java
public class samr { /** * Private constructor to prevent instantiation of utility class. */ private samr() { // Utility class } /** * Returns the RPC interface syntax UUID and version for SAMR protocol. * * @return The SAMR interface UUID string */ public static String getSyntax() { return "12345778-1234-abcd-ef00-0123456789ac:1.0"; }Created: Sat Dec 20 13:44:44 GMT 2025 - Last Modified: Sat Aug 16 01:32:48 GMT 2025 - 23.4K bytes - Click Count (0) -
src/main/java/jcifs/smb1/dcerpc/msrpc/samr.java
public class samr { /** * Private constructor to prevent instantiation of utility class. */ private samr() { // Utility class } /** * Returns the RPC interface syntax UUID and version for SAMR protocol. * * @return The SAMR interface UUID string */ public static String getSyntax() { return "12345778-1234-abcd-ef00-0123456789ac:1.0"; }Created: Sat Dec 20 13:44:44 GMT 2025 - Last Modified: Sat Aug 16 01:32:48 GMT 2025 - 23.1K bytes - Click Count (0)