Zakalwe posted:

3000 lines is , but there's nothing wrong with using the occasional goto. "Never ever use goto" is generally promulgated by people who've heard of Dijkstra's article but never read the drat thing.

subreality posted:

The same guy also wrote a login.php that went a little something like this:

php:

<?
  $logged_in = false;

  $users = mysql_query("SELECT * FROM users");

  while ($row = mysql_fetch_assoc($users)) {
    if ($row['username'] == $_POST['username'] && $row['password'] == $_POST['password']) {
      $user_id = $row['id'];
      $logged_in = true;
    }
  }
?>

Zakalwe posted:

code:

bool is_odd(const int a)
{
        return( a%2 == 0);
}

The Evan posted:

"I've set up a massive switch statement that consists of all the prime numbers up to 271"

He hard-coded a LUT for primes. Mother of god. Somewhere in my deep dark past, I recall reading an optimization suggestion that checking prime-ness is so easy computationally that making a table is a complete waste of memory, even ROM.

What made him stop at 271, anyway?

Lexical Unit posted:

Exhibit 3

code:

int pants_size = 0; // global
int pants_type = 0; // global

void handle_pants_event(int size, int type)
{
	if (pants_size == 0 && pants_type == 0)
	{
		pants_type = type;
		pants_size = size;
	}
	else if (pants_size != size || pants_type != type)
	{
		pants_type = type;
		pants_size = size;
	}
}

dancavallaro posted:

The Something Awful Forums > Discussion > Serious Hardware / Software Crap > The Cavern of COBOL > WOW6432 Megathread?

MrMoo posted:

while (0) is used to allow a semicolon after the macro call, it's pretty much the only place it should be used.

Avenging Dentist posted:

Congrats on being ignorant.

quote:

Who is this hexadecimal you all keep implying I am, which I am not?

Argue posted:

Okay, here comes another wonderful piece of architecture from our client, incidentally a very large company that's well-known in my country.

There's an HTTP server running, and it listens for requests such as "reset PIN#". When the server receives such a request, it dumps the connection into a pool, and queues up the request for processing by another thread, the service thread.

Now, the service thread does its processing (which is partly what my previous posts were about), and generates a response. How do you suppose this response gets sent back to the original requester?

That's right! It doesn't! Instead, it just plucks any connection out of the pool, and returns the response there. The results are exactly as you might expect. One guy might receive a "successful" confirmation message when his transaction failed, and vice versa.

yaoi prophet posted:

If I ever write a language this will be a compile-time error.

Wheany posted:

code:

//not needed anymore
/*
function someFunction(){

}
function someOtherFunction(){

}
function yetAnotherfunction(){

}
*/

NotShadowStar posted:

And that's why you always, always, always use equals equals equals in javascript!

TRex EaterofCars posted:

Yeah it does. In both 2005 and 2008 R2 at least.

Open SSMS, go find a table, right click on it, Script Table as >, SELECT To >, New Query Editor Window. Commas first.

angrytech posted:

Wait, there's supposed to be a turtle in that gif?

w00tz0r posted:

"Forward compatibility is easy, all Microsoft products are completely forward compatible. I can write a program on Windows Vista and have it run on Windows 95. The only thing that broke forwards compatibility is UAC."

tef posted:

also, 'ruby is written in c so it's fast'

Threep posted:

Dicky B posted:

indie_game_developers.txt posted:

fully block all incoming attacks.

Zombywuf posted:

Aside from that, what the hell are you doing in that other 95ms? Seriously? Factoring the user's IP address?

quote:

Javascript thinks that 64.99 * 100 is 6498.999999... Go ahead, try it any way you like. If someone can explain this, I'll be eternally grateful.
submitted 2 hours ago by collin_ph

quote:

I don't think you understand how floats are stored in memory. Click on any of the links posted and read up on it.

redditor collin_ph posted:

I'm wondering who's bright idea it was to do this. It's funny after programming for nearly 30 years, I run into this TODAY. Makes me feel kind of dumb-- however, I wonder how people avoid this type of thing with MONEY.

...


I'm an Oracle certified DBA, worked for the government for about 16 years, and most recently as an IS manager.

Golbez posted:

God help you if you order the same amount of something twice in one day.

plushpuffin posted:

Just got this gem the other day from the senior developer / project lead:

code:

public class MyClass
{
    /// <remarks>
    /// It's okay to make this static because
    /// MyClass is only used as a singleton, but
    /// I wish I didn't have to make it public, too.
    /// </remarks>
    public static HashSet<int> SomeSetModifiedByMultipleThreads;
}

Zhentar posted:

I don't know about faster, but it's definitely easier to use a dummy date and write

SQL code:

WHERE @date BETWEEN table.START_DATE AND table.END_DATE

than it is to write

SQL code:

WHERE @date BETWEEN table.START_DATE AND table.END_DATE
	OR @date >= table.START_DATE ANd table.END_DATE IS NULL

Bunny Cuddlin posted:

I have a Kinect sensor attached to my computer and I wrote an app that sits between my PC and the database server and it only allows me to run destructive commands if I do a little voodoo dance and say a magic word can we get off this please

Aleksei Vasiliev posted:

I've never seen this in a Java library, but .NET loves it and I loving despise it.

quote:

*Name interfaces with nouns or noun phrases, or adjectives that describe behavior. For example, the interface name IComponent uses a descriptive noun. The interface name ICustomAttributeProvider uses a noun phrase. The name IPersistable uses an adjective.
*Use Pascal case.
*Use abbreviations sparingly.
*Prefix interface names with the letter I, to indicate that the type is an interface.
*Use similar names when you define a class/interface pair where the class is a standard implementation of the interface. The names should differ only by the letter I prefix on the interface name.
*Do not use the underscore character (_).

DAT NIGGA HOW posted:

If this guy is as smart about crypography as he makes himself out to be with his tone in the article, they why is he spending his time writing blog posts? Why should I trust this guy's assessment at all? Maybe if he had an alternative that other experts can either agree is done right, then I'll listen to him. Otherwise its just blogspam.

Crypography is the kind of thing where if you understand the concepts, building a cryptocat site is trivial. If you don't understand the concepts, then cryptography is hard.

Just writing a blogpost saying "the devs of cryptocat are idiots that don't understand anything about crypography dont use it". OK... gee thanks for the tip random internet stranger. It just kinda reeks of monday morning quarterbacking to me...

Pilsner posted:

Heh, I thought of that too. Other annoying variations are "exc". Or naming it when it's not even used is bad.

Shinku ABOOKEN posted:

I am guilty of using PROGRA~1 more than once. Escaping paths is

E: This was on 32bit and for personal purposes only thankfully.

Monkeyseesaw posted:

This may be unpopular but I think git is a bit of a coding horror in the fact that it fails to really hide any details of its implementation and makes source control more complicated than it should be. I really didn't grok git until I realized my branches were pointers and my commits were nodes in a graph. I've never had to understand the internals of any source control system like that before.

This is coming from someone who uses git at work and likes git and understands how it's more empowering than, say, SVN but the learning curve on it is much sharper than it could (and should) be.