3 ms·
> Java having a Mardown parser within its compiler just seems wildly out of scope for not a lot of benefit. It won't. The `javadoc` tool parses doc comments a
by kelnos 3y ago
> Java having a Mardown parser within its compiler just seems wildly out of scope for not a lot of benefit.
It won't. The `javadoc` tool parses doc comments and outputs HTML, not `javac`.
> This seems like the use case of an IDE extension, or a website that host code
Disagree. I find often enough that I read Java code in vim or simply using less or cat. Having doc comments that are more readable would be helpful. And it seems silly that every website code hosting solution should have to implement a javadoc parser, when a much simpler solution exists: use markup that is readable as-is.
If you don't want to use this, that's fine; you can continue writing your javadoc comments as you have in the past. That's no reason to suggest that the rest of us should be stuck in the past.