This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29341 - [XP31] "Unreadable" sounds too strong and opinionating, for lack of a better word
Summary: [XP31] "Unreadable" sounds too strong and opinionating, for lack of a better ...
Status: RESOLVED MOVED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-17 16:34 UTC by Abel Braaksma
Modified: 2015-12-18 11:15 UTC (History)
0 users

See Also:


Attachments

Description Abel Braaksma 2015-12-17 16:34:59 UTC
(OT: the online translator gave "ballyhoo" for the Dutch "stemmingmakerij", but I doubt that's a proper expression. I just mean to say that the word, as used in that sentence, reads as the view of the writer, which I think we should try to prevent.)

Section 3.22 Arrow operator:

This syntax is particularly helpful when conventional function call syntax is unreadable...

I prefer something like:

This syntax is particularly helpful when conventional function call syntax may make code harder to read....

Perhaps I'm a bit over-pedantic, not a big deal I guess, but I find "unreadable" quite strong, besides, we have lived with this older syntax for over a decade and managed quite well ;).
Comment 1 Abel Braaksma 2015-12-18 11:15:45 UTC
This is now addressed under #29346. Not a duplicate, so I resolve this as MOVED.