- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 13 Feb 2010 12:21:38 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8967 Summary: Why is the optional argument in the middle? Isn't it more convenient when copy/pasting code to make optional modifications at either end without having to precisely place the cursor somewhere in the middle? Particularly for piecing together arguments, too Product: HTML WG Version: unspecified Platform: Other URL: http://www.whatwg.org/specs/web-apps/current- work/#posting-messages OS/Version: other Status: NEW Severity: normal Priority: P3 Component: HTML5 spec bugs AssignedTo: dave.null@w3.org ReportedBy: contributor@whatwg.org QAContact: public-html-bugzilla@w3.org CC: ian@hixie.ch, mike@w3.org, public-html@w3.org Section: http://www.whatwg.org/specs/web-apps/current-work/#posting-messages Comment: Why is the optional argument in the middle? Isn't it more convenient when copy/pasting code to make optional modifications at either end without having to precisely place the cursor somewhere in the middle? Particularly for piecing together arguments, too, since one could append the mandatory arguments first, and then if somewhere else some ports are required simple + them to the string. Admittedly, this would be crafting a string which then would have to be executed. And what about having an array of arguments? The second item is sometimes one argument, and sometimes another. So an array of arrays couldn't handled simply (e.g. sometime [1], other times [2]) when processing posts to multiple different domains and potential ports. Admittedly that be a rather informative filling multiple forms from multiple domains, but isn't that potentially desirable? Posted from: 72.253.36.224 -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Saturday, 13 February 2010 12:21:39 UTC