- Sort Score
- Result 10 results
- Languages All
Results 141 - 150 of 225 for sintaxe (0.17 sec)
-
LICENSES/third_party/forked/gotestsum/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 Apr 01 18:49:15 UTC 2022 - 11.1K bytes - Viewed (0) -
LICENSES/vendor/github.com/go-logr/stdr/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: Sun Sep 18 01:47:24 UTC 2022 - 11.2K bytes - Viewed (0) -
src/main/java/jcifs/smb/SmbFileInputStream.java
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 30 05:58:03 UTC 2025 - 15.6K bytes - Viewed (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.
Registered: Sun Sep 07 03:35:12 UTC 2025 - Last Modified: Wed Sep 11 20:39:30 UTC 2013 - 11.1K bytes - Viewed (0) -
docs/en/docs/tutorial/first-steps.md
* the path `/` * using a <abbr title="an HTTP GET method"><code>get</code> operation</abbr> /// info | `@decorator` Info That `@something` syntax in Python is called a "decorator". You put it on top of a function. Like a pretty decorative hat (I guess that's where the term came from). A "decorator" takes the function below and does something with it.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 11K bytes - Viewed (0) -
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) -
src/main/java/jcifs/smb1/dcerpc/msrpc/srvsvc.java
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 26.3K bytes - Viewed (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.
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Tue May 08 21:35:34 UTC 2018 - 11.1K bytes - Viewed (0) -
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) -
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)