Skip to content

Commit a8abb5d

Browse files
committed
Javadoc: remove redundant </p> tags, text URL to link
1 parent 3b8d66e commit a8abb5d

File tree

1 file changed

+3
-7
lines changed

1 file changed

+3
-7
lines changed

src/main/java/io/kaitai/struct/ByteBufferKaitaiStream.java

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -86,14 +86,13 @@ public ByteBufferKaitaiStream(ByteBuffer buffer) {
8686
* which the associated type was parsed, because the underlying {@link ByteBuffer} might
8787
* contain the data of all parent types and such as well and not only the one the caller is
8888
* actually interested in.
89-
* </p>
9089
* <p>
9190
* The returned {@link ByteBuffer} is always rewinded to position 0, because this stream was
9291
* most likely used to parse a type already, in which case the former position would have been
9392
* at the end of the buffer. Such a position doesn't help a common reading user much and that
9493
* fact can easily be forgotten, repositioning to another index than the start is pretty easy
9594
* as well. Rewinding/repositioning doesn't even harm performance in any way.
96-
* </p>
95+
*
9796
* @return read-only {@link ByteBuffer} to access raw data for the associated type.
9897
*/
9998
public ByteBuffer asRoBuffer() {
@@ -115,22 +114,19 @@ public ByteBuffer asRoBuffer() {
115114
* references to it, which breaks all subsequent <code>read..</code> methods with
116115
* {@link NullPointerException}. Afterwards, a call to {@link System#gc()} will
117116
* typically release the mmap, if garbage collection will be triggered.
118-
* </p>
119117
* <p>
120118
* There is a <a href="https://bugs.java.com/bugdatabase/view_bug.do?bug_id=4724038">
121119
* JDK-4724038 request for adding unmap method</a> filed at Java bugtracker since 2002,
122120
* but as of 2018, it is still unresolved.
123-
* </p>
124121
* <p>
125122
* A couple of unsafe approaches (such as using JNI, or using reflection to invoke JVM
126123
* internal APIs) have been suggested and used with some success, but these are either
127124
* unportable or dangerous (may crash JVM), so we're not using them in this general
128125
* purpose code.
129-
* </p>
130126
* <p>
131127
* For more examples and suggestions, see:
132-
* https://stackoverflow.com/questions/2972986/how-to-unmap-a-file-from-memory-mapped-using-filechannel-in-java
133-
* </p>
128+
* <a href="https://stackoverflow.com/questions/2972986/how-to-unmap-a-file-from-memory-mapped-using-filechannel-in-java">How to unmap a file from memory mapped using FileChannel in java?</a>
129+
*
134130
* @throws IOException if FileChannel can't be closed
135131
*/
136132
@Override

0 commit comments

Comments
 (0)