- From: <bugzilla@jessica.w3.org>
- Date: Tue, 04 Nov 2014 21:49:46 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26958 --- Comment #20 from Michael Kay <mike@saxonica.com> --- Concerning comments #16 and #18, the specification frequently uses terms such as "creates", "constructs", and "new" when referring to objects such as strings and sequences that have no existential identity; I think the main purpose of this is to cater to a readership that is accustomed to sequences and even strings being mutable. The language used for maps and arrays has continued this tradition, perhaps even more emphatically to avoid any danger that people familiar with other languages will interpret operations such as remove() as mutations. I quite agree that it's not really appropriate; it would be much better to say "Returns a sequence that..." or "Returns a string that... " or "Returns a map in which...". Unfortunately getting rid of the term "constructor functions" is rather more difficult. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 4 November 2014 21:49:47 UTC