Alert icon
We're changing our privacy policy. This stuff matters.  Learn more  Dismiss

code injection [2/2]

Loading...

Sign in or sign up now!
Alert icon
Upgrade to the latest Flash Player for improved playback performance. Upgrade now or more info.
1,035
Loading...
Alert icon
Sign in or sign up now!
Alert icon

Uploaded by on Mar 16, 2008

second part. see first part for description.

Category:

Science & Technology

Tags:

License:

Standard YouTube License

  • likes, 1 dislikes

Link to this comment:

Share to:
see all

All Comments (2)

Sign In or Sign Up now to post a comment!
  • Very interesting.

    I think you might be even more caffinated than I.

    While the system I'm helping design uses primarily interpreted code, similar concepts apply to the compiled stuff. This really solidified that we're starting with the right set of libraries.

  • What you're doing is altering function/procedure pointers. These are known as "callbacks," particularly in user interface implementations. Oberon message dispatchers are an example.

    This isn't injecting code anywhere. Code injection implies that you're directly uploading code into the address space of another module. Since Oberon seals a module once it's compiled, all you can do to alter a module's behavior is pass function pointers.

Loading...
Alert icon
0 / 00Unsaved Playlist Return to active list
    1. Your queue is empty. Add videos to your queue using this button:
      or sign in to load a different list.
    Loading...Loading...Saving...
    • Clear all videos from this list
    • Learn more