Talk:Case-sensitivity of identifiers: Difference between revisions

From Rosetta Code
(We could add a category for case sensitivity)
m (moved Talk:Three Dogs to Talk:Three dogs: capitalization policy)
(No difference)

Revision as of 13:58, 12 May 2011

  • The task description needs to state what is needed to complete the task.
  • Maybe a more descriptive title? Something like "Variable case sensitivity"?

--Paddy3118 06:03, 7 February 2011 (UTC)

Variable name case sensitivity” is probably better still. (Mind you, hardly anyone uses case insensitive variable contents any more; some ideas are better off dying.) –Donal Fellows 09:44, 7 February 2011 (UTC)
Yes... for better or worse, case insensitivity under unicode can be nightmarish (as can be just about anything else that wants to treat characters abstractly and consistently). --Rdm 15:57, 7 February 2011 (UTC)
I nominate "Variable identifier case sensitivity". We can of course have redirects from other candidates. --Mwn3d 20:13, 7 February 2011 (UTC)
Hi, identifier just doesn't roll off the tongue for me; and my sugestion isn't as good as that of Dkf, so I'd go +1 on Variable name sensitivity with a redirect for the others. --Paddy3118 22:43, 7 February 2011 (UTC)
How about Case sensitive variable names?, including the end question mark. --Paddy3118 22:43, 7 February 2011 (UTC)
That would probably be the first page on RC with a question mark in its name. I don't know that that's a precedent I want to set. Moreover, we're producing descriptions of whether languages are case-sensitive in this area, not asking; statements, not (for the most part) questions… –Donal Fellows 22:55, 7 February 2011 (UTC)

We could add a category for case sensitivity and place the task in that category. Markhobley 15:53, 26 April 2011 (UTC)