Total Members Voted: 183
function wordsFromBeginning(%txt, %n){ return getWords(%txt, 0, %n);}$text = "Hello world, how are you?";for(%a = 5; %a >= 0; %a -= 2) echo(wordsFromBeginning($text, %a) SPC wordsFromBeginning($text, %a - 1));7 lines, go ahead and try it out
I can't tell if this style is too different or not.
Using lines as a basis for anything is pointless.function foo() { ... } function bar() { ... } for (...) { if (...) quit(); }
sorry, let me say that differently: lines can be used as a low-weight metric in addition to a number of other things to assign a proper threat level
Maybe have a middle-level type of reviewer? One that has the ability to approve but only for mods/updates that are very low threat level.
Anything formatted like this should be instantly failed for handicapation, and line endings should be automatically converted to CR + LF to prevent issues like this.And by "this," I mean containing 4 statements or more on a single line.That's better :p
Well, if we do deep brown townysis on the mods for the brown townysis anyway, we could use statements as the metric instead of SLoC.
IMO, I think there should be a fourth class for the lowest, people that just comment on the add-on.
It doesn't make sense for this to be anything but either public or just the review team.I don't know which it will be, but...
i mean, people will definitely be able to comment on the mod after release, that's a given
is an auto-updater implemented? if not, you should implement it asap so we don't have to continuously go to the website to download a simple update.
What I was saying is that if enough people complain about a bug then it should notify the author of the mod to fix the add-on.