Can we please burninate the variables tag?
What is the point in it?
We know that programs have variables!
There is no need for over 15.5K posts to be tagged variables...
-
2For a second there I thought that said "Burninate [vegetables]".– aleJan 18, 2013 at 14:44
-
Ehhh same thing @AlEverett :-P– NaftaliJan 18, 2013 at 14:44
-
7What about the sidekick [constants] ?– MatJan 18, 2013 at 14:55
-
@Mat not as bad (only 1K) but still should probably be burninated.– NaftaliJan 18, 2013 at 14:56
-
3Its at 15k now, and I can't say i've seen a single enlightening use of the tag.– TextmodeAug 29, 2013 at 16:52
Add a comment
|
1 Answer
I agree this should be burninated.
As Mat pointed out there's a side-kick constants. However this isn't the only tag playing Robin to variables Batman.
There are a number of other contenders:
- The parameters, c5.5k: param, parameters, params.
- The local variables, 212: local-variables.
- The global variables, c1.8k: global-variables, globals (superglobals?).
answered Jan 18, 2013 at 15:06
-
-
1[superglobals] should probably stay. I wouldn't be against one tag for each of local vars, global vars & function parameters (but at most one each). For things like scoping/lifetime/concurrency questions? Maybe. Not sure. I'll probably disagree with myself on those tomorrow (:– MatJan 18, 2013 at 15:27
-
I was tempted to put in optional-parameters, optional-parameters etc etc @mat but I thought I might disagree with myself tomorrow... Jan 18, 2013 at 15:35
-
3I would argue the good boundary is if it's reasonable to assume it will be used in every program. So get rid of variables, local-variables, and parameters, but leave the others.– LattyJan 18, 2013 at 16:18