The code for today's show is available as a ZIP for download.
Snubs Compiled
Nathan Follmer's link
http://bjorn.tipling.com/if-programming-languages-were-weapons https://plus.google.com/u/0/+NathanFollmer/posts/VqW2afWKYFF Nathan's Fibonacci sequencer
https://projecteuler.net/problem=2 https://plus.google.com/u/0/+NathanFollmer/posts/9K2tLFxR1SnIvory Tower
Classes Recap
A "class" is a blue print that can be created multiple times. When the blue print is used to create -- it creates an "OBJECT of that class We can create as many objects of a class, and when we're done with it, it's removed from memory. If classes are blueprints --- things that are ready to create --- to turn into objects, then "ABSTRACT Classes" are architectural designs. They have the right shape of the thing to be created They have much of the information needed to create the thing being created But they are not complete They cannot be instantiated - (They cannot not be "created" into an object) The sole purpose of an abstract class is to act as a "base" for inheritance They cannot be instantiated, but a derivative class, which inherits the abstract members from the abstract class, can be. That derivative class must provide proper implementation for all the abstract members of the abstract class, then it CAN create an object. (It complete's the blueprints) An Interface is like an Abstract class in that it can be used to define hierarchies for any sub-classes Unlike an Abstract Class, an Interface has NO body. -- It's just the definitions of methods, with no body whatsoever. Hosts: Fr. Robert Ballecer, SJ and Shannon Morse
Subscribe and get Coding 101 automatically at https://twit.tv/shows/coding-101 Follow PadreSJ and Snubs on Twitter Bandwidth for Coding 101 is provided by CacheFly.