RTFJD (the JavaDocs are your friends!) If you haven't read them in a long time, then RRTFJD (they might have changed!)
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:Shades of the dinosaurs! You're actually proposing to patch a Java class?!!!
Jesse, gotos are an inherent part of bytecodes. Bytecodes are the assembly-language of Java and are too low-level to support structured programming constructs.
Brennan, if you are using an intelligent build environment like Maven, only the initial build should take "hours". The system is smart enough that unless you do a "clean" operation between builds, only the changed parts should actually get recompiled.
Hours seems a bit exaggerated, though for Java. I've built some pretty big projects and probably had them take no more than 20 minutes, absolute tops. For hours, I'd have to build in something like C, where, for example the FreeCAD project probably takes at least half an hour and I don't want to think about doing that on a slow machine like a Raspberry Pi! I'm pretty sure I can build a Linux kernal in less time!
RTFJD (the JavaDocs are your friends!) If you haven't read them in a long time, then RRTFJD (they might have changed!)
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
wikipedia wrote:The original patch program was written by Larry Wall (who went on to create the Perl programming language) and posted to mod.sources[1] (which later became comp.sources.unix) in May 1985. A variant of the program (but not the only one)[2][3][4] is part of the GNU project[5] and is maintained by the FSF.
RTFJD (the JavaDocs are your friends!) If you haven't read them in a long time, then RRTFJD (they might have changed!)
RTFJD (the JavaDocs are your friends!) If you haven't read them in a long time, then RRTFJD (they might have changed!)
Matthew Bendford wrote:
As for low-level patching in more general: I once had a look into how "no cd cracks" are done for games. Well, depending on how many checks are in the game code it takes quite some time to find and "patch" the all, even with tools designed to help to semi-automate this process. But also drm protection goes the self-modifying code route like denuvo: during runtime it randomly adds drm checks into running code while not crashing to ASLR. It's a play of chicken between developers and pirates going back to the 70s.
Jesse Silverman wrote:I did tons and tons of disassembly of 68000 code from boot-loaded Atari ST games in the late 80's into the early 90's.
I keep hearing that getting compilable Java source from byte code is ever-decreasingly practical.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
RTFJD (the JavaDocs are your friends!) If you haven't read them in a long time, then RRTFJD (they might have changed!)
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |