So if you want to decode an x86 instruction, first you should grab all the prefix bytes. Then you get the first byte of the opcode, and if it's a 2byte one get the second one. Then if the instruction has non-implicit non-immediate operands get the Mod R/M byte. If the address mode is memory and the base register is esp, get the SIB. If there's a memory displacement get it, and if there's an immediate operand get that.
Name:
Anonymous2008-05-09 7:40
the current batch of challenges is NOT entertaining. the problem with these challenges is not that they exist, it's that they are created by people who are unqualified to do so.
just because you like to participate in online challenges, doesn't mean you're good at creating them. in fact, you're probably interested in these things because you're too bored to come up with something to do on your own.
that's fine, really, but don't expect people to put any effort into creating a program that they're not going to use. if you want to start a challenge: wait until you have a *GREAT* idea, announce it as such, and i will join it.
another option would be to recognize your own strengths and weaknesses, and wait for me to start my challenge :)
Name:
Anonymous2008-05-09 9:19
As you can see, the problem with this style is that each layer gets cluttered with passing all the information that the lower layers need. Bundling related bits of information into tuples or records helps to some extent. In this example you can see it’s been done already; scriptOptions, miscOptions and configFlags are bundles of other parameters. (The name miscOptions is a sure sign that we’re bundling arbitrary things together just to try and reduce the number of parameters we’re passing.)
>>5 ITT Post in this thread when /prog/ is crap then i'd have to make two posts every time because this thread sucks
Unable to understand English?
Also, ITT post in this thread? ...
Note: For a discussion on why replicated code, such as that in the if structure of the procedural solution, is bad see Kent Beck's discussion on OnceAndOnlyOnce on the Wiki Wiki Web.
While this solves the problem, it would not be easy to modify in the future if the problem changes. In particular, if we need to add new operating systems, we need to extend the if structure. If we want to add additional functionality for each operating system, we would likely see this expand to nested if statements.
Of course, using the ENTERPRISE way that he came up with, you only need to create a new file with a singleton class implementing BoxSpecifier, then register the new class in the static {} section of the OSDiscriminator class.
AND THIS IS WHAT JAVA PROGRAMMERS ACTUALLY BELIEVE.
No wonder every piece of shit ever written in Java is so damn slow. Jesus fuck, I'm going to go throw up now.
Name:
Anonymous2008-05-09 20:01
>>7
He should come up with a better example, because I couldn't stop thinking "Map/Dictionary/Hashtable" through the whole thing.
>>12
Isn't it sad that he actually used a Hashmap to store his horrible objects when he could have just used it to store his list of OS identifiers and his statement about each of them, rather then engaging in his ENTERPRISE Object factory clusterfuck. He should also look into GENERICS for a much better solution.
Joseph Bergin, Ph.D.
The hardest troll known to man.
Name:
Anonymous2008-05-11 14:03
What the fuck is all of this "raid /code/" bullshit? Do you, sad stupid idiot that is trying to be so fucking cool, realize that ALMOST EVERY SINGLE POSTER ON /prog/ is a poster on channel 4? Nevermind. Fuck all of you guys.
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy