That Turkey Story posted:

A little side story -- I've seen someone do this before when he was first learning to program and when I told him that he didn't need the parenthesis because return is not a function, he said that he was using the parenthesis not because he thought it was a function but because he wasn't sure of the order of operations. For instance, he thought return 1 + 3; might return the value 1 and then the rest of the expression was evaluated "after the return" and therefore not affecting the return value (in other words he thought return 1 + 3 could potentially behave something like (return 1) + 3 where "return 1" returned the value 1 and had a value in the encapsulating expression of 1). I was kind of puzzled for a second, but I was actually sort of impressed when I heard his rationale since it showed both that he questioned the effect of a type of return statement he had never seen before, as up until then he probably had only seen 1 term return statements, and he also realized that by using parenthesis there he could more safely assume the result that he wanted. He is now actually a very good programmer!

Of course, that was someone who had only just started programming a week before, so he had an excuse to not know the behavior, and if I saw any experienced programmer doing it I'd definitely be a little bit more baffled (though honestly who really cares, some extra parenthesis never hurt anyone).

zootm posted:

Like (return 1 + 2); or return (1 + 2);? I think in C-like languages I'd regard the former as something of a coding horror simply because it's so unusual that I wouldn't even know if it worked. Really strange.

Drx Capio posted:

std::vector<bool> AFAIK is almost always implemented as a bitfield that uses proxy objects to modify its 'bool references'. I doubt that the 31 bits you save per bool really add up to anything significant, but it's a simple solution at least.

Drx Capio posted:

No, that's just a viable alternative if you're retarded and don't want to go with the prime factorization solution. Why would you use dynamic memory at runtime when you can quickly run through a sieve of eratosthenes and get some valid, unique flags?

king_kilr posted:

He's not looking for things that multiple together uniquely, it's addition.(I think)

TSDK posted:

What if, now hear me out guys, what if we use this compression scheme where we represent each prime by a particular power of two. So the i-th prime is encoded as 2^i, and then add these together to represent which primes are factors of the number we're compressing.

king_kilr posted:

What about 1, 4, 7 any addition of these numbers will be a unique sum(unless you need to add the same value multiple times, in which case primes are the only option).

JoeNotCharles posted:

Jesus, what is it with you and your fetish for bitmaps?

Mr.Radar posted:

The person who wrote that probably cut their teeth with VB6 and wasn't aware of the ?: operator. VB6 didn't have a dedicated short-circuiting inline conditional operator, but it included a (non-short-circuiting IIRC) IIF function that worked like the one you posted.

stack posted:

This makes me cry

code:

@empty($someVar)

@isset($someVar)

What error are you trying to suppress? If the value doesn't exist they'll return false. isset() for the love of pete exists to check if a value 'is set'.

Also this hurts me

code:

if(!isset($bravo)) $blah = here($something);
elseif(isset($charlie)) $blah = here($charlie);
else $blah = nothere();

Whitespace is free goddamnit. A couple pairs of braces couldn't hurt either.

New code is committed daily that is littered with examples and uses of the above.

Jethro posted:

Unless you're using an 80 line monitor for some terminal from the '80s, there is no such thing as "wasting a line."

JoeNotCharles posted:

What's wrong with this? The only weird thing I can see is that db.Open is called after creating the transaction, but that doesn't have anything to do with your comment so I assume that's just the way the API works.

Vanadium posted:

As posted in ##c++ on freenode:

code:

iteration_begin:
std::vector<CGameEvent*>::iterator lIterator = mEvents.begin();
for(lIterator; lIterator != mEvents.end(); lIterator++)
{
	if((*lIterator)->Dirty())
	{
		DestroyEvent(*lIterator);
		//Yes this is a shame, but once we remove an element the iterator is invalidated
		// there is for sure a better way to handle this, we do not want to only break
		// as this would keep the remaining event from being iterated
		goto iteration_begin;
	}
	(*lIterator)->OnIterate(inDeltaT);
}

deimos posted:

Calling Nebby here to ILLUSTRATE TO YOUR PLEBE BRAIN how SUPERIOR HUNGARIAN NOTATION is.

Ryouga Inverse posted:

Okay, look, there's a difference between there possibly being edge cases in which it can be used and...

code:

        private void ReadIniFile()
        ....

I mean, I feel like I'm reading Ruby or something, except ugly.

Ryouga Inverse posted:

Zakalwe posted:

That's not a horror, that's a savage optimisation for an operation done a lot in many renderers. Low accuracy bitwise hack combined with one Newton-Raphson iteration.

wrok posted:

code:

    foreach (string item in _ptAttributeDic.Keys)
    {
        string val = _ptAttributeDic[item];
        switch (item.ToLower())
        {
            case "mail":
                if (string.IsNullOrEmpty(base._email))
                    base._email = val;
                break;
            
            case "facsimiletelephonenumber":
                base._faxNum = val;
                break;
            
            case "telephonenumber":
                base._phoneNumber = val;
                break;
        }
    }

Scaevolus posted:

Serious question, have you ever used C, C++, C#, or Java?

king_kilr posted:

Guys you should be using ruby so you can just monkeypatch a to_radians and to_degrees functions onto int.

Captain Capacitor posted:

I'm guilty of nondescript variables in two ways: Loop variables and isolated variables in methods/procedures under 5 lines or so (for example, getters/setters).

What's the general opinion on short variable names that are explained/in limited context?

code:

def averageLoginCount():
  q = query = User.objects.all()
  q = q.filter(firstname__contains='y')
  q = q.aggregate(Avg('login_count'))
  return q