Your example wouldn't work on Windows 95, but it did work on DOS and Windows up to 3.11 (not Windows NT). The PC architecture, and the Microsoft series of operating systems, started with the Intel 8086 processor and an operating system (DOS) designed to run a single program at a time.
The Fall and Rise of SVGSometime in 1998, a former co-worker who had gone to work at Adobe came by my office at Bertlesmann to inform me of a brand new technology that she knew would excite me: PGML, or “Precision Graphics Markup Language.” This was the Adobe flavor of XML for Vector Graphics.
Six Essential Tips For Async - IntroductionIf you understand the basic flow of control in an async method, then those three points all fall naturally into place. This first introduction video explains that control flow. Slides and source code are available on Lucian's blog.
The dangers of ThreadLocalLanguages and frameworks evolve. We as developers have to learn new things constantly and unlearn already-learned knowledge. Speaking for myself, unlearning is the most difficult part of continuous learning. When I first came into contact with multi-threaded applications in .
The hard part of error handling is not the error itselfAre our discussions about errors focusing on the right part of the problem? We tend to argue about what exceptions mean, or how return values are messy. But if I look at a lot of code the actual capturing of the error isn’t the most difficult part. It’s everything surrounding it.
Saturday Morning Breakfast CerealAlgorithms, Etc. by January 2015 revision This page contains lecture notes and other course materials for various algorithms classes I have taught at the University of Illinois, Urbana-Champaign.
Faking the TCP handshakeTo the best of our knowledge, this attack is a new finding. Asking around, people assume the TCP handshake verifies the IP addresses on both sides. This attack shows that this is not actually true.
What text books tell you about inheritance in OOP is wrongI received an email from one of my students asking for a design advice. He is working on an application used by a sports team manager, where they can create, edit and delete players, teams and coaches. So, the design that my student had in mind is something like this UML diagram:
This Read-It-Later-list is just that, bookmarks of stuff I intend to read or have read. I do not necessarily agree with opinions or statements in the bookmarked articles.
This list is compiled from my Pocket list.