| 
									
										
										
										
											2024-09-10 21:00:33 +02:00
										 |  |  | // VIM_TEST_SETUP unlet! g:java_no_tab_space_error g:java_ignore_javadoc
 | 
					
						
							|  |  |  | // VIM_TEST_SETUP unlet! g:java_no_trail_space_error
 | 
					
						
							|  |  |  | // VIM_TEST_SETUP let [g:java_space_errors,g:java_comment_strings]=[1,1]
 | 
					
						
							| 
									
										
										
										
											2024-09-30 19:40:04 +02:00
										 |  |  | // VIM_TEST_SETUP let g:java_ignore_markdown = 1
 | 
					
						
							| 
									
										
										
										
											2024-09-10 21:00:33 +02:00
										 |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | // VIM_TEST_SETUP setlocal spell fdc=2 fdl=64 fdm=syntax fen
 | 
					
						
							|  |  |  | // VIM_TEST_SETUP highlight link javaCommentStart Todo
 | 
					
						
							|  |  |  | // VIM_TEST_SETUP highlight link javaCommentTitle Underlined
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
											  
											
												runtime(java): Recognise the inline kind of the {@return} tag (#14284)
Also:
- Refine comment matching (javaComment{Error\ and,Start}).
- Continue rewriting regexps (prefer atom grouping with
  non-capturing parens; factor out common prefixes in
  alternations).
- Allow for relative paths with the _file_ attribute of
  {@snippet}.
- Anticipate HTML in the @see tags.
- Match the nullary method parens in javaDocSeeTagParam.
- Improve the boundary patterns for summary sentences of
  documentation.
> This sentence ends at ... or at the first tag (as defined
> below).
There are Java documentation tags (@) and there are HTML
tags (<?>) (with Markdown looming large; see JEP 467).  With
block tags, e.g. @param, @return, @see, we begin another
documentation "sentence" whether or not the author has
terminated the summary sentence with a period; with
.<!-- -->, we may follow abbreviations, enumerations,
initials, (but instead consider @literal or  ) _within_
the summary sentence.  On the other hand, inline tags, e.g.
@code, @link, @literal, should not terminate the summary
sentence.
References:
https://bugs.openjdk.org/browse/JDK-8075778
https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#firstsentence
https://docs.oracle.com/en/java/javase/21/docs/specs/javadoc/doc-comment-spec.html
Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
											
										 
											2024-03-25 18:18:28 +03:00
										 |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2024-09-30 19:40:04 +02:00
										 |  |  | /**/ /*/ */ /* /*/ /*/*/ /*//*/ /** HTML comment tests.
 | 
					
						
							| 
									
										
											  
											
												runtime(java): Recognise the inline kind of the {@return} tag (#14284)
Also:
- Refine comment matching (javaComment{Error\ and,Start}).
- Continue rewriting regexps (prefer atom grouping with
  non-capturing parens; factor out common prefixes in
  alternations).
- Allow for relative paths with the _file_ attribute of
  {@snippet}.
- Anticipate HTML in the @see tags.
- Match the nullary method parens in javaDocSeeTagParam.
- Improve the boundary patterns for summary sentences of
  documentation.
> This sentence ends at ... or at the first tag (as defined
> below).
There are Java documentation tags (@) and there are HTML
tags (<?>) (with Markdown looming large; see JEP 467).  With
block tags, e.g. @param, @return, @see, we begin another
documentation "sentence" whether or not the author has
terminated the summary sentence with a period; with
.<!-- -->, we may follow abbreviations, enumerations,
initials, (but instead consider @literal or  ) _within_
the summary sentence.  On the other hand, inline tags, e.g.
@code, @link, @literal, should not terminate the summary
sentence.
References:
https://bugs.openjdk.org/browse/JDK-8075778
https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#firstsentence
https://docs.oracle.com/en/java/javase/21/docs/specs/javadoc/doc-comment-spec.html
Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
											
										 
											2024-03-25 18:18:28 +03:00
										 |  |  |  * <p>There is no entry point method {@code main}:
 | 
					
						
							| 
									
										
										
										
											2024-09-30 19:40:04 +02:00
										 |  |  |  * {@snippet file = HTMLSnippets.java region = main id = _01}
 | 
					
						
							| 
									
										
											  
											
												runtime(java): Recognise the inline kind of the {@return} tag (#14284)
Also:
- Refine comment matching (javaComment{Error\ and,Start}).
- Continue rewriting regexps (prefer atom grouping with
  non-capturing parens; factor out common prefixes in
  alternations).
- Allow for relative paths with the _file_ attribute of
  {@snippet}.
- Anticipate HTML in the @see tags.
- Match the nullary method parens in javaDocSeeTagParam.
- Improve the boundary patterns for summary sentences of
  documentation.
> This sentence ends at ... or at the first tag (as defined
> below).
There are Java documentation tags (@) and there are HTML
tags (<?>) (with Markdown looming large; see JEP 467).  With
block tags, e.g. @param, @return, @see, we begin another
documentation "sentence" whether or not the author has
terminated the summary sentence with a period; with
.<!-- -->, we may follow abbreviations, enumerations,
initials, (but instead consider @literal or  ) _within_
the summary sentence.  On the other hand, inline tags, e.g.
@code, @link, @literal, should not terminate the summary
sentence.
References:
https://bugs.openjdk.org/browse/JDK-8075778
https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#firstsentence
https://docs.oracle.com/en/java/javase/21/docs/specs/javadoc/doc-comment-spec.html
Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
											
										 
											2024-03-25 18:18:28 +03:00
										 |  |  |  * <p>There is no textual representation:
 | 
					
						
							| 
									
										
										
										
											2024-09-30 19:40:04 +02:00
										 |  |  |  * {@snippet class = HTMLSnippets region = toString id = _02} */
 | 
					
						
							|  |  |  | class HTMLCommentsTests implements Comparable<HTMLCommentsTests>
 | 
					
						
							|  |  |  | {	// JDK 21+.
 | 
					
						
							|  |  |  | 	private HTMLCommentsTests() { }
 | 
					
						
							| 
									
										
										
										
											2024-09-10 21:00:33 +02:00
										 |  |  | 
 | 
					
						
							| 
									
										
											  
											
												runtime(java): Recognise the inline kind of the {@return} tag (#14284)
Also:
- Refine comment matching (javaComment{Error\ and,Start}).
- Continue rewriting regexps (prefer atom grouping with
  non-capturing parens; factor out common prefixes in
  alternations).
- Allow for relative paths with the _file_ attribute of
  {@snippet}.
- Anticipate HTML in the @see tags.
- Match the nullary method parens in javaDocSeeTagParam.
- Improve the boundary patterns for summary sentences of
  documentation.
> This sentence ends at ... or at the first tag (as defined
> below).
There are Java documentation tags (@) and there are HTML
tags (<?>) (with Markdown looming large; see JEP 467).  With
block tags, e.g. @param, @return, @see, we begin another
documentation "sentence" whether or not the author has
terminated the summary sentence with a period; with
.<!-- -->, we may follow abbreviations, enumerations,
initials, (but instead consider @literal or  ) _within_
the summary sentence.  On the other hand, inline tags, e.g.
@code, @link, @literal, should not terminate the summary
sentence.
References:
https://bugs.openjdk.org/browse/JDK-8075778
https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#firstsentence
https://docs.oracle.com/en/java/javase/21/docs/specs/javadoc/doc-comment-spec.html
Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
											
										 
											2024-03-25 18:18:28 +03:00
										 |  |  | 	/** No-op, i. e. no operation.
 | 
					
						
							|  |  |  | 	* ({@literal@literal} may be used with {@code .} for contraction.)
 | 
					
						
							|  |  |  | 	* @return {@code null} */
 | 
					
						
							|  |  |  | 	Void noOp1() { return null; }
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/** No-op, i.e. no operation.
 | 
					
						
							|  |  |  | 	* ({@literal<!-- -->} may be used after {@code .} for contraction.)
 | 
					
						
							|  |  |  | 	* @return {@code null} */
 | 
					
						
							|  |  |  | 	Void noOp2() { return null; }
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/** No-op, i.e\u002e no operation.
 | 
					
						
							|  |  |  | 	* ({@literal\u005cu002e} is processed early, use alternatives.)
 | 
					
						
							|  |  |  | 	* @return {@code null} */
 | 
					
						
							|  |  |  | 	Void noOp3() { return null; }
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/** No-op, i.e{@literal .} no operation.
 | 
					
						
							|  |  |  | 	* @return {@code null} */
 | 
					
						
							|  |  |  | 	Void noOp4() { return null; }
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/** No-op, i.e.<!-- --> no operation.
 | 
					
						
							|  |  |  | 	* @return {@code null} */
 | 
					
						
							|  |  |  | 	Void noOp5() { return null; }
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/** No-op, i.e. no operation.
 | 
					
						
							|  |  |  | 	* @return {@code null} */
 | 
					
						
							|  |  |  | 	Void noOp6() { return null; }
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/** {@return {@code null}, with no-op, i.e. no operation} */
 | 
					
						
							|  |  |  | 	Void noOp7() { return null; }
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/** {@return {@code null}, with no-op, i.e. no operation}.. */
 | 
					
						
							|  |  |  | 	Void noOp8() { return null; }
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/** {@return {@code null}, with no-op, i.e. no operation} . . */
 | 
					
						
							|  |  |  | 	Void noOp9() { return null; }
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2024-09-30 19:40:04 +02:00
										 |  |  | 	/** {@return the major Java version}
 | 
					
						
							|  |  |  | 	 * @hidden */
 | 
					
						
							| 
									
										
										
										
											2024-09-10 21:00:33 +02:00
										 |  |  | 	protected int majorVersion() { return 21; }
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/** {@summary Compares this instance with the passed {@code that}
 | 
					
						
							|  |  |  | 	 * instance for order by invoking {@link Integer#compare(int, int)
 | 
					
						
							|  |  |  | 	 * compare} and passing it {@code this.majorVersion()} and
 | 
					
						
							|  |  |  | 	 * {@code that.majorVersion()} as respective @arguments.}
 | 
					
						
							|  |  |  | 	 * {@inheritDoc} */
 | 
					
						
							| 
									
										
										
										
											2024-09-30 19:40:04 +02:00
										 |  |  | 	@Override public int compareTo(HTMLCommentsTests that)
 | 
					
						
							| 
									
										
										
										
											2024-09-10 21:00:33 +02:00
										 |  |  | 	{
 | 
					
						
							|  |  |  | 		java.util.Objects.requireNonNull(that, "that");
 | 
					
						
							|  |  |  | 		return Integer.compare(this.majorVersion(),
 | 
					
						
							|  |  |  | 						that.majorVersion());
 | 
					
						
							|  |  |  | 	}
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2024-09-30 19:40:04 +02:00
										 |  |  | 	/// Returns an empty string for an @Override annotated method
 | 
					
						
							|  |  |  | 	/// (see Chapter 9.6.4.4 {@literal @Override} in a Java Language
 | 
					
						
							|  |  |  | 	/// Specification) overridden from `java.lang.Object`
 | 
					
						
							|  |  |  | 	///
 | 
					
						
							|  |  |  | 	/// @return an empty string /// No period for the above summary!
 | 
					
						
							|  |  |  | 	private String asString() { return ""; }
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
											  
											
												runtime(java): Recognise the inline kind of the {@return} tag (#14284)
Also:
- Refine comment matching (javaComment{Error\ and,Start}).
- Continue rewriting regexps (prefer atom grouping with
  non-capturing parens; factor out common prefixes in
  alternations).
- Allow for relative paths with the _file_ attribute of
  {@snippet}.
- Anticipate HTML in the @see tags.
- Match the nullary method parens in javaDocSeeTagParam.
- Improve the boundary patterns for summary sentences of
  documentation.
> This sentence ends at ... or at the first tag (as defined
> below).
There are Java documentation tags (@) and there are HTML
tags (<?>) (with Markdown looming large; see JEP 467).  With
block tags, e.g. @param, @return, @see, we begin another
documentation "sentence" whether or not the author has
terminated the summary sentence with a period; with
.<!-- -->, we may follow abbreviations, enumerations,
initials, (but instead consider @literal or  ) _within_
the summary sentence.  On the other hand, inline tags, e.g.
@code, @link, @literal, should not terminate the summary
sentence.
References:
https://bugs.openjdk.org/browse/JDK-8075778
https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#firstsentence
https://docs.oracle.com/en/java/javase/21/docs/specs/javadoc/doc-comment-spec.html
Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
											
										 
											2024-03-25 18:18:28 +03:00
										 |  |  | 	/** Returns an empty string for an @Override annotated method
 | 
					
						
							|  |  |  | 	* (see Chapter 9.6.4.4 {@literal @Override} in a Java Language
 | 
					
						
							|  |  |  | 	* Specification) overridden from <code>java.lang.Object</code>
 | 
					
						
							|  |  |  | 	*
 | 
					
						
							|  |  |  | 	* @return an empty string */// No period for the above summary!
 | 
					
						
							| 
									
										
										
										
											2024-09-30 19:40:04 +02:00
										 |  |  | 	@Override public String toString() { return asString(); }
 | 
					
						
							| 
									
										
											  
											
												runtime(java): Recognise the inline kind of the {@return} tag (#14284)
Also:
- Refine comment matching (javaComment{Error\ and,Start}).
- Continue rewriting regexps (prefer atom grouping with
  non-capturing parens; factor out common prefixes in
  alternations).
- Allow for relative paths with the _file_ attribute of
  {@snippet}.
- Anticipate HTML in the @see tags.
- Match the nullary method parens in javaDocSeeTagParam.
- Improve the boundary patterns for summary sentences of
  documentation.
> This sentence ends at ... or at the first tag (as defined
> below).
There are Java documentation tags (@) and there are HTML
tags (<?>) (with Markdown looming large; see JEP 467).  With
block tags, e.g. @param, @return, @see, we begin another
documentation "sentence" whether or not the author has
terminated the summary sentence with a period; with
.<!-- -->, we may follow abbreviations, enumerations,
initials, (but instead consider @literal or  ) _within_
the summary sentence.  On the other hand, inline tags, e.g.
@code, @link, @literal, should not terminate the summary
sentence.
References:
https://bugs.openjdk.org/browse/JDK-8075778
https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#firstsentence
https://docs.oracle.com/en/java/javase/21/docs/specs/javadoc/doc-comment-spec.html
Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
											
										 
											2024-03-25 18:18:28 +03:00
										 |  |  | }
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2024-09-30 19:40:04 +02:00
										 |  |  | // javadoc --snippet-path . --source-path . -d /tmp/html_docs/ -package \
 | 
					
						
							|  |  |  | // 	-tag 'jls:a:See Java Language Specification:' HTMLSnippets.java
 | 
					
						
							|  |  |  | /** Snippets for HTML comment tests. */
 | 
					
						
							|  |  |  | class HTMLSnippets
 | 
					
						
							| 
									
										
											  
											
												runtime(java): Recognise the inline kind of the {@return} tag (#14284)
Also:
- Refine comment matching (javaComment{Error\ and,Start}).
- Continue rewriting regexps (prefer atom grouping with
  non-capturing parens; factor out common prefixes in
  alternations).
- Allow for relative paths with the _file_ attribute of
  {@snippet}.
- Anticipate HTML in the @see tags.
- Match the nullary method parens in javaDocSeeTagParam.
- Improve the boundary patterns for summary sentences of
  documentation.
> This sentence ends at ... or at the first tag (as defined
> below).
There are Java documentation tags (@) and there are HTML
tags (<?>) (with Markdown looming large; see JEP 467).  With
block tags, e.g. @param, @return, @see, we begin another
documentation "sentence" whether or not the author has
terminated the summary sentence with a period; with
.<!-- -->, we may follow abbreviations, enumerations,
initials, (but instead consider @literal or  ) _within_
the summary sentence.  On the other hand, inline tags, e.g.
@code, @link, @literal, should not terminate the summary
sentence.
References:
https://bugs.openjdk.org/browse/JDK-8075778
https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#firstsentence
https://docs.oracle.com/en/java/javase/21/docs/specs/javadoc/doc-comment-spec.html
Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
											
										 
											2024-03-25 18:18:28 +03:00
										 |  |  | {	/* 	TRAILING BLANKS AND MESSPILLINGS ARE SIGNIFICANT! */
 | 
					
						
							| 
									
										
										
										
											2024-09-30 19:40:04 +02:00
										 |  |  | 	private HTMLSnippets() { }
 | 
					
						
							| 
									
										
										
										
											2024-09-10 21:00:33 +02:00
										 |  |  | 
 | 
					
						
							| 
									
										
											  
											
												runtime(java): Recognise the inline kind of the {@return} tag (#14284)
Also:
- Refine comment matching (javaComment{Error\ and,Start}).
- Continue rewriting regexps (prefer atom grouping with
  non-capturing parens; factor out common prefixes in
  alternations).
- Allow for relative paths with the _file_ attribute of
  {@snippet}.
- Anticipate HTML in the @see tags.
- Match the nullary method parens in javaDocSeeTagParam.
- Improve the boundary patterns for summary sentences of
  documentation.
> This sentence ends at ... or at the first tag (as defined
> below).
There are Java documentation tags (@) and there are HTML
tags (<?>) (with Markdown looming large; see JEP 467).  With
block tags, e.g. @param, @return, @see, we begin another
documentation "sentence" whether or not the author has
terminated the summary sentence with a period; with
.<!-- -->, we may follow abbreviations, enumerations,
initials, (but instead consider @literal or  ) _within_
the summary sentence.  On the other hand, inline tags, e.g.
@code, @link, @literal, should not terminate the summary
sentence.
References:
https://bugs.openjdk.org/browse/JDK-8075778
https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#firstsentence
https://docs.oracle.com/en/java/javase/21/docs/specs/javadoc/doc-comment-spec.html
Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
											
										 
											2024-03-25 18:18:28 +03:00
										 |  |  | 	/** The method {@code main} must be declared {@code public}, {@code
 | 
					
						
							| 
									
										
										
										
											2024-03-22 21:32:48 +03:00
										 |  |  | 	 * static}, and {@code void}.  It must specify a formal parameter
 | 
					
						
							|  |  |  | 	 * whose declared type is array of {@link String}.  Therefore,
 | 
					
						
							| 
									
										
										
										
											2024-09-10 21:00:33 +02:00
										 |  |  | 	 * <em>either</em> of the following declarations is acceptable:
 | 
					
						
							| 
									
										
										
										
											2024-03-22 21:32:48 +03:00
										 |  |  | 	 * 	{@snippet lang="java":
 | 
					
						
							|  |  |  | 	 * // @highlight substring="main" type="italic":
 | 
					
						
							|  |  |  | 	 * public static void main(String[] args) { }
 | 
					
						
							|  |  |  | 	 * }<br /><pre class="snippet">
 | 
					
						
							|  |  |  | 	 *{@code public static void main(String... args) { }}</pre>
 | 
					
						
							|  |  |  | 	 *
 | 
					
						
							|  |  |  | 	 * @param args optional commande-line arguments 
 | 
					
						
							| 
									
										
											  
											
												runtime(java): Recognise the inline kind of the {@return} tag (#14284)
Also:
- Refine comment matching (javaComment{Error\ and,Start}).
- Continue rewriting regexps (prefer atom grouping with
  non-capturing parens; factor out common prefixes in
  alternations).
- Allow for relative paths with the _file_ attribute of
  {@snippet}.
- Anticipate HTML in the @see tags.
- Match the nullary method parens in javaDocSeeTagParam.
- Improve the boundary patterns for summary sentences of
  documentation.
> This sentence ends at ... or at the first tag (as defined
> below).
There are Java documentation tags (@) and there are HTML
tags (<?>) (with Markdown looming large; see JEP 467).  With
block tags, e.g. @param, @return, @see, we begin another
documentation "sentence" whether or not the author has
terminated the summary sentence with a period; with
.<!-- -->, we may follow abbreviations, enumerations,
initials, (but instead consider @literal or  ) _within_
the summary sentence.  On the other hand, inline tags, e.g.
@code, @link, @literal, should not terminate the summary
sentence.
References:
https://bugs.openjdk.org/browse/JDK-8075778
https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#firstsentence
https://docs.oracle.com/en/java/javase/21/docs/specs/javadoc/doc-comment-spec.html
Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
											
										 
											2024-03-25 18:18:28 +03:00
										 |  |  | 	 * @jls 12.1.4 Invoke {@code Test.main} */
 | 
					
						
							|  |  |  | 	// @start region = main		
 | 
					
						
							| 
									
										
										
										
											2024-03-22 21:32:48 +03:00
										 |  |  | 	// @link substring = 'String' target = 'java.lang.String' :
 | 
					
						
							|  |  |  | 	public static void main(String[] args) { }
 | 
					
						
							| 
									
										
											  
											
												runtime(java): Recognise the inline kind of the {@return} tag (#14284)
Also:
- Refine comment matching (javaComment{Error\ and,Start}).
- Continue rewriting regexps (prefer atom grouping with
  non-capturing parens; factor out common prefixes in
  alternations).
- Allow for relative paths with the _file_ attribute of
  {@snippet}.
- Anticipate HTML in the @see tags.
- Match the nullary method parens in javaDocSeeTagParam.
- Improve the boundary patterns for summary sentences of
  documentation.
> This sentence ends at ... or at the first tag (as defined
> below).
There are Java documentation tags (@) and there are HTML
tags (<?>) (with Markdown looming large; see JEP 467).  With
block tags, e.g. @param, @return, @see, we begin another
documentation "sentence" whether or not the author has
terminated the summary sentence with a period; with
.<!-- -->, we may follow abbreviations, enumerations,
initials, (but instead consider @literal or  ) _within_
the summary sentence.  On the other hand, inline tags, e.g.
@code, @link, @literal, should not terminate the summary
sentence.
References:
https://bugs.openjdk.org/browse/JDK-8075778
https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#firstsentence
https://docs.oracle.com/en/java/javase/21/docs/specs/javadoc/doc-comment-spec.html
Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
											
										 
											2024-03-25 18:18:28 +03:00
										 |  |  | 	// @end 
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2024-09-10 21:00:33 +02:00
										 |  |  | 	/** {@return an empty string}
 | 
					
						
							| 
									
										
											  
											
												runtime(java): Recognise the inline kind of the {@return} tag (#14284)
Also:
- Refine comment matching (javaComment{Error\ and,Start}).
- Continue rewriting regexps (prefer atom grouping with
  non-capturing parens; factor out common prefixes in
  alternations).
- Allow for relative paths with the _file_ attribute of
  {@snippet}.
- Anticipate HTML in the @see tags.
- Match the nullary method parens in javaDocSeeTagParam.
- Improve the boundary patterns for summary sentences of
  documentation.
> This sentence ends at ... or at the first tag (as defined
> below).
There are Java documentation tags (@) and there are HTML
tags (<?>) (with Markdown looming large; see JEP 467).  With
block tags, e.g. @param, @return, @see, we begin another
documentation "sentence" whether or not the author has
terminated the summary sentence with a period; with
.<!-- -->, we may follow abbreviations, enumerations,
initials, (but instead consider @literal or  ) _within_
the summary sentence.  On the other hand, inline tags, e.g.
@code, @link, @literal, should not terminate the summary
sentence.
References:
https://bugs.openjdk.org/browse/JDK-8075778
https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#firstsentence
https://docs.oracle.com/en/java/javase/21/docs/specs/javadoc/doc-comment-spec.html
Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
											
										 
											2024-03-25 18:18:28 +03:00
										 |  |  | 	 * @see <a href="https://docs.oracle.com/javase/specs/jls/se21/html/jls-3.html#jls-3.10.5">3.10.5 String Literals</a>
 | 
					
						
							| 
									
										
										
										
											2024-09-30 19:40:04 +02:00
										 |  |  | 	 * @see
 | 
					
						
							|  |  |  | 	 * <a href="https://docs.oracle.com/javase/specs/jls/se21/html/jls-4.html#jls-4.3.2">4.3.2 The Class Object</a>
 | 
					
						
							| 
									
										
										
										
											2024-09-10 21:00:33 +02:00
										 |  |  | 	 * @see java.base/java.lang.Object#toString() */
 | 
					
						
							| 
									
										
											  
											
												runtime(java): Recognise the inline kind of the {@return} tag (#14284)
Also:
- Refine comment matching (javaComment{Error\ and,Start}).
- Continue rewriting regexps (prefer atom grouping with
  non-capturing parens; factor out common prefixes in
  alternations).
- Allow for relative paths with the _file_ attribute of
  {@snippet}.
- Anticipate HTML in the @see tags.
- Match the nullary method parens in javaDocSeeTagParam.
- Improve the boundary patterns for summary sentences of
  documentation.
> This sentence ends at ... or at the first tag (as defined
> below).
There are Java documentation tags (@) and there are HTML
tags (<?>) (with Markdown looming large; see JEP 467).  With
block tags, e.g. @param, @return, @see, we begin another
documentation "sentence" whether or not the author has
terminated the summary sentence with a period; with
.<!-- -->, we may follow abbreviations, enumerations,
initials, (but instead consider @literal or  ) _within_
the summary sentence.  On the other hand, inline tags, e.g.
@code, @link, @literal, should not terminate the summary
sentence.
References:
https://bugs.openjdk.org/browse/JDK-8075778
https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#firstsentence
https://docs.oracle.com/en/java/javase/21/docs/specs/javadoc/doc-comment-spec.html
Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
											
										 
											2024-03-25 18:18:28 +03:00
										 |  |  | 	// @start region = toString	
 | 
					
						
							|  |  |  | 	// @replace substring = '""' replacement = "\u0022\u0022"
 | 
					
						
							|  |  |  | 	// @link regex = '\bString' target = java.lang.String type = linkplain :
 | 
					
						
							|  |  |  | 	@Override public String toString() { return ""; }
 | 
					
						
							|  |  |  | 	// @end 
 | 
					
						
							| 
									
										
										
										
											2024-03-22 21:32:48 +03:00
										 |  |  | }
 |