In this case, there were clear signs of an object-oriented approach (data and functions were located around each other in memory, which is not likely to happen in non-OO languages, etc).
I agree with the gist of your statement, but I don't think the OOP source-level organization of "data close to methods" is reflected in the generated machine code or the intermediate assembly. I'd wager data would be placed in non-executable memory segments, far from where the code ('text') resides. When you print out values of pointers you can often recognize what lives on the stack, what is heap-based data and what is a function pointer just by looking at address ranges.
You know, I wonder if the antivirus suites of the future will be able to see stuff like this being written. Like "oh no, he is using emacs/vi and writing a php injection script - perhaps this is something we should look into specifically".
Had you clicked the the link to the PDF provided in the summary, you'd have stumbled onto their paper -- as in "the thing we're discussing here" -- where they mention Spanish and Hebrew were also studied.
is they barely interact with anything. The fact they barely interact with anything makes them hard to detect. Even places like the LHC need to generate assloads of neutrinos to see them.
I'm not familiar with that unit of measurement. Is it specific to neutrino quantities or can it be used for other things? Oh, and could you give a conversion to something more familiar, like Libraries of Congress or Football Fields?:D
It can, but you don't want to know.
I don't know the conversion factor to Libraries of Congress, but I think it's about 0.3 goatse.
Yeah, but the files are unlinked right after they're created so it's not as if they hanging around the filesystem.
There's no such thing as "right after" in a time-sharing system where multitasking is not cooperative. Unless the creation-and-unlinking happens atomically, which I doubt is the case, the process doing the unlinking can be preempted "right before" trying to do that.
if you're running an OS that doesn't let you do much, and the BIOS is locked, then you're not going to accomplish anything without cracking the thing open.
Well, there's this trick where they irradiate the RAM in your laptop or perhaps heat the CPU without cracking the laptop open, hoping for the right bit to flip in the RAM or the right register in the CPU and voila, suddenly you're executing attacker's privileged code. I'm not saying that's easy, but it's been demonstrated to be viable. The PC is not cracked open, and they've accomplished something.
Re:advantages of multiple inheritance
on
PHP 5.4 Released
·
· Score: 1
Nah, I never said there is something to be accomplished by doing that. I was just surprised by your assertion that one must use jmp/jxx or call and friends to change the instruction pointer. I honestly thought that one could push and pop eip if one wanted.
Re:advantages of multiple inheritance
on
PHP 5.4 Released
·
· Score: 1
Only if you are using an assembly language that lets you directly modify the program counter with normal arithmetic instructions. x86 does not let you do this. You must use one of the jmp family of instructions (essentially goto), or call/int/ret/iret (and related).
So what exactly prevents you from pushing the instruction pointer, popping a usual register, doing arithmetics on it, pushing it back to the stack and popping the modified instruction pointer?
Why can't you highlight more than one item? Either of the following works perfectly:
- Click an item, hold shift and use arrow keys to select a range
- Click an item, hold shift and click another item to select a range
- Click anywhere except but an item and drag a selection box
- Click first item, ctrl+click every other item to be highlighted
- Hover item and click '+'-overlay on every item to be highlighted
- Ctrl+a to select all
- A plethora of combinations of the above as well as other methods I've probably missed
How this can present a problem to you is beyond me...
What I meant was "you need to use a function to concatenate strings" is just the tip of the iceberg. There is a more of it under the surface of the water, starting with "these are not really strings, but pointers to null-terminated arrays of characters", "you must ensure there's enough room for the result", "the dimension of the result must be known at compile time or you'll have to use malloc" and ugly under-the-hood stuff like that.
My adventure with programming too began with BASIC. As I progressed through Pascal to C and then to C++, I remember C's strings as one of the worst nightmares for a newb.
I don't know JavaScript, so I can't comment on that.
Slashdot Mirror
One of the few old technologies that's likely to stay with us forever.
Twenty billion years isn't forever.
And just how, pray tell, do you think they measure the mass of the bars Mr. Nitpicker? Some elaborate physics experiment?
Think about it.
Here's a hint: http://visual.merriam-webster.com/science/measuring-devices/measure-weight/beam-balance.php
Can you describe what a centimeter is, relative to something else?
How's this - it's the length of one edge of a cube that contains one gram of water.
At what temperature?
I use IMPLICIT NONE, you insensitive clod.
In this case, there were clear signs of an object-oriented approach (data and functions were located around each other in memory, which is not likely to happen in non-OO languages, etc).
I agree with the gist of your statement, but I don't think the OOP source-level organization of "data close to methods" is reflected in the generated machine code or the intermediate assembly. I'd wager data would be placed in non-executable memory segments, far from where the code ('text') resides. When you print out values of pointers you can often recognize what lives on the stack, what is heap-based data and what is a function pointer just by looking at address ranges.
You know, I wonder if the antivirus suites of the future will be able to see stuff like this being written. Like "oh no, he is using emacs/vi and writing a php injection script - perhaps this is something we should look into specifically".
Real programmers use cat anyway :).
Had you clicked the the link to the PDF provided in the summary, you'd have stumbled onto their paper -- as in "the thing we're discussing here" -- where they mention Spanish and Hebrew were also studied.
the android merge means i can play angry birds without having to use wine...
Note that playing sober raises it to another level of difficulty.
You mean he had his own PRNG and didn't know how its random() behaved?
Turns out on compiler 'a' random() doesn't return a value from 0 to the maximum value of a long, but returns up to a value less than the maximum value
One word: RAND_MAX. http://linux.die.net/man/3/random
the definition of "more private".
Kingdom for a mod point.
And something to wipe my coffee from the screen with.
What do you know exactly about my subdemographic?
That is has no INTERESTING, for one :).
You do realize this is not an English sentence, right?
I do. That was my point.
What do you know exactly about my subdemographic?
That is has no INTERESTING, for one :).
is they barely interact with anything. The fact they barely interact with anything makes them hard to detect. Even places like the LHC need to generate assloads of neutrinos to see them.
I'm not familiar with that unit of measurement. Is it specific to neutrino quantities or can it be used for other things? Oh, and could you give a conversion to something more familiar, like Libraries of Congress or Football Fields? :D
It can, but you don't want to know.
I don't know the conversion factor to Libraries of Congress, but I think it's about 0.3 goatse.
All my machines have a floppy.
I don't understand how adding a peripheral can make the machine "worse"?
I don't understand how adding a third nipple. Oh wait...
posting to undo moderation.
Yeah, but the files are unlinked right after they're created so it's not as if they hanging around the filesystem.
There's no such thing as "right after" in a time-sharing system where multitasking is not cooperative. Unless the creation-and-unlinking happens atomically, which I doubt is the case, the process doing the unlinking can be preempted "right before" trying to do that.
if you're running an OS that doesn't let you do much, and the BIOS is locked, then you're not going to accomplish anything without cracking the thing open.
Well, there's this trick where they irradiate the RAM in your laptop or perhaps heat the CPU without cracking the laptop open, hoping for the right bit to flip in the RAM or the right register in the CPU and voila, suddenly you're executing attacker's privileged code. I'm not saying that's easy, but it's been demonstrated to be viable. The PC is not cracked open, and they've accomplished something.
Nah, I never said there is something to be accomplished by doing that. I was just surprised by your assertion that one must use jmp/jxx or call and friends to change the instruction pointer. I honestly thought that one could push and pop eip if one wanted.
Only if you are using an assembly language that lets you directly modify the program counter with normal arithmetic instructions. x86 does not let you do this. You must use one of the jmp family of instructions (essentially goto), or call/int/ret/iret (and related).
So what exactly prevents you from pushing the instruction pointer, popping a usual register, doing arithmetics on it, pushing it back to the stack and popping the modified instruction pointer?
No, you need True, False, and Null
Or True, False and FileNotFound. http://thedailywtf.com/Articles/What_Is_Truth_0x3f_.aspx
Why can't you highlight more than one item? Either of the following works perfectly:
- Click an item, hold shift and use arrow keys to select a range
- Click an item, hold shift and click another item to select a range
- Click anywhere except but an item and drag a selection box
- Click first item, ctrl+click every other item to be highlighted
- Hover item and click '+'-overlay on every item to be highlighted
- Ctrl+a to select all
- A plethora of combinations of the above as well as other methods I've probably missed
How this can present a problem to you is beyond me...
You probably missed this bit:
the keyboard is usually on a shelf.
What I meant was "you need to use a function to concatenate strings" is just the tip of the iceberg. There is a more of it under the surface of the water, starting with "these are not really strings, but pointers to null-terminated arrays of characters", "you must ensure there's enough room for the result", "the dimension of the result must be known at compile time or you'll have to use malloc" and ugly under-the-hood stuff like that.
My adventure with programming too began with BASIC. As I progressed through Pascal to C and then to C++, I remember C's strings as one of the worst nightmares for a newb.
I don't know JavaScript, so I can't comment on that.
I think C is an excellent language to learn programming basics. It's simple and small.
However, problems start when you get to explaining string concatenation.