Xenogenesis posted:

OT: I present beautiful handwritten SQL for a small Rails app:

code:

      query = %Q{
        SELECT DISTINCT ON (s.user_id, s.chart_id) s.*
          FROM scores AS s
          JOIN charts AS c
            ON (c.id = s.chart_id)
            #{chart ?
            "WHERE c.id = ?" :
            "WHERE c.key_id = ?
              AND c.game_id = ?"
            }
        AND s.id IN (
          SELECT s2.id
          FROM scores AS s2
          LEFT JOIN scores AS s3
            ON (s2.chart_id = s3.chart_id
                AND s2.user_id = s3.user_id
                AND s2.judgement < s3.judgement)
          WHERE s2.chart_id = s.chart_id
            AND s3.judgement IS NULL
          ORDER BY s2.judgement, s2.score DESC
          #{"LIMIT ?" unless limit.nil?})
        ORDER BY s.user_id, s.chart_id, s.judgement, s.score DESC
      }

Xenogenesis posted:

Hahaha, you wish that join was useless.

Hammerite posted:

I don't see what's wrong with that. Isn't it just an operator precedence issue? In many situations it is necessary to use brackets to enforce the desired order of operations. This seems no different.

HFX posted:

Implicit type conversion, or how you get to laugh at someone when they tell you C++ is strongly typed.

pseudorandom name posted:

Consider what happens when e.g. a smart pointer template class implements operator bool and you compare two different instantiations of that template for equality.

MrMoo posted:

I tried using external MASM64 only to find that the supported syntax can be very different to MASM, i.e. MASM64 is like a version 1.0 and MASM32 is a version 8.0 with a lot more features. If you trawl the MSDN forums you can find tidbits from the developers.

"Augmented assignment statements posted:

An augmented assignment evaluates the target (which, unlike normal assignment statements, cannot be an unpacking) and the expression list, performs the binary operation specific to the type of assignment on the two operands, and assigns the result to the original target. The target is only evaluated once.

An augmented assignment expression like x += 1 can be rewritten as x = x + 1 to achieve a similar, but not exactly equal effect. In the augmented version, x is only evaluated once. Also, when possible, the actual operation is performed in-place, meaning that rather than creating a new object and assigning that to the target, the old object is modified instead.

With the exception of assigning to tuples and multiple targets in a single statement, the assignment done by augmented assignment statements is handled the same way as normal assignments. Similarly, with the exception of the possible in-place behavior, the binary operation performed by augmented assignment is the same as the normal binary operations.

Zombywuf posted:

Look at the graph for the part before the Perl one goes crazy.

Biowarfare posted:

code:

try {
	// Everything
}

catch (e) {}

Wheany posted:

Holy poo poo, yes you can:

code:

span[style="text-decoration:underline; color:red; background:yellow"]{
	color:green !important;
	background:blue !important;
	text-decoration:none !important;
}

BigRedDot posted:

Oh, this was 100% the case there. "But we're a research lab, you see!" Or "We make sonars, not software!" Nevermind everything past the actual physical sensor is all built with software nowadays...

OddObserver posted:

... Though really, bringing back Pascal might actually not be a horrible idea, either (after adding a string type, of course).

Jabor posted:

It's the whole lambda scoping thing. Lambdas close over variables, not values.

Ensign Expendable posted:

Is e some kind of insane list of lists (of lists)?

Brecht posted:

'abstract' is not a C++ keyword? What is this?

shrughes posted:

No because foo is virtual.

shrughes posted:

So you say that string("hi") and string("hey") are of different types.

shrughes posted:

Zamujasa posted:

As for MySQL, Lua seems to have the opposite problem where a few people pronounce it "L-U-A" when it's actually pronounced "loo-ah".

Munkeymon posted:

If you need access to an object in the finally block of a try, you have to declare it outside of the try, but you do not have to instantiate it outside the try.

baquerd posted:

Or suppose you want a placeholder member variable at the object level that will be defined in constructor arguments:

code:

class foo {
  final Object butts;
  foo(Object butts) {
     this.butts = butts;
  }

Why would you want an instantiated butts at declaration? Hint: you wouldn't and it would actually break this.

Vanadium posted:

This whole discussion would be moot if more people realised that when you say Object variable; in C# you're saying Object^ variable; in C++/CLI which is fundamentally different.

Vanadium posted:

So the real horror here is that C++ gives you the option of defining a default constructor for on-the-stack, value, non-reference types? Cripes!

Toady posted:

bar doesn't hold a reference a stack-allocated Object?

Xenogenesis posted:

https://code.google.com/p/phpreboot/

Surely this is some brilliant troll?

yaoi prophet posted:

I think my favorite part is how curly braces are used both for control flow and for delimiting code from HTML. Also raw XPath and URIs, both of which contain the end-of-line comment token

pokeyman posted:

I really don't understand why someone would see two options, "require semicolons" and "don't require semicolons", and decide to go right down the middle. Sometimes it's ok to pick one!

TasteMyHouse posted:

Apparently, in VC++6, this worked: