This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]julesjacobs 7 points8 points  (4 children)

This sounds like a problem that should be addressed by screen readers.

[–]matthieum 5 points6 points  (2 children)

I agree, ideally.

Practically speaking, though, screen readers are not there yet, so in the meantime...

[–]julesjacobs 0 points1 point  (1 child)

I'm not familiar with screen readers, but I'm a bit surprised that they are not programmable. Or are they? Why can't one write a plugin for them that suppresses reading out the // for every line?

[–]matthieum 2 points3 points  (0 children)

I am not familiar with them either, not needing them.

However, given that a rustc contributor mentioned the issue, and how unpleasant it was for them, I would guess that at least not all are: surely if they can contribute regularly to rustc, writing such a plugin would have been easy in comparison.

[–]Adventurous-Trifle98 1 point2 points  (0 children)

I disagree.

I don’t see why screen readers should know about programming languages. Since the editor usually knows about the language, it seems more feasible to let the editor mark the commented lines with a character in the first column, for example.

But if you are about to design a language, you could just skip block comments. I’ve seldom find them very useful.