Forgot your password?

Comment: Re:Well, if you're going to push... (Score 1) 129

by flargleblarg (#47913855) Attached to: Court Rules the "Google" Trademark Isn't Generic

More to the point, when people use, "Google," as a verb, they mean to actually use Google, as opposed to using any brand of facial tissue available when saying, "Kleenex."

Exactly! You can't google something using Bing, for example. Not that you'd want to anyway. You can only google something using Google.

(Now I feel like I need to go wash my hands after mentioning Bing. Eww.)

Comment: Re:A solution in search of a problem... (Score 1) 324

Don't feel bad. It's tricky wording. I wasn't sure how to word it to be clear (and to be fair, I don't think it was really clear). "Opposites" to me would imply 180 opposing... so I wrote "mirror-opposites" to imply a vertical mirror, but of course that's pretty subtle and not very unambiguous.

Comment: Re: Would be nice to see Scala replace Java (Score 1) 94

by flargleblarg (#47854831) Attached to: Scala Designer Martin Odersky On Next Steps
I'm pretty sure, though, that even any class that requires you to use equals(), you can still use == as a fast-precheck. That is, a==b implies a.equals(b) for all objects a,b in all classes. The converse, of course, is not the case: a.equals(b) does not imply a==b. And the inverse is not true: a!=b does not imply !a.equals(b). But the contra-positive is true: !a.equals(b) does imply a!=b.

Comment: Re:+ operator for string concat? (Score 1) 727

Yes "clever" operator overloading comes up high in my list. Scripting languages are full of it like in Pike: str/" " Divide a string by space to get an array of the words. But I dislike it way more when operator overloading abuse is done in user code than when it is a language construct.

So, if you take that array of words and multiply it back by " ", do you get the original string? Because that would make it cool.

Comment: Re:C++03 had one that was corrected in C++11. (Score 1) 727

Namely, the >> symbol. Because templates use angle brackets for template parameters, if you had a nested template such as T<int, T1<double> >, you HAD to put the space between the two closing angle brackets. Otherwise the lexer would interpret the two angle brackets as the shift operator.

That's a really dumbass lexer. Glad that shit got fixed.

Comment: Re:Powershell (Score 1) 727

They should of used:



I know one game shipped with buggy AI because somebody forgot to use two equal signs inside an if statement!

That's not C's fault. That's the developer's fault for ignoring the compiler warning about it. (Or for not having enabled the warning.)

Yes, we will be going to OSI, Mars, and Pluto, but not necessarily in that order. -- Jeffrey Honig