I'm trying to understand OOP so I can write better OOP code and one thing which keeps coming up is this concept of a delegate (using .NET). I could have an object, which is totally self contained (encapsulated); it knows nothing of the outside world... but then I attach a delegate to it. 

In my head, this is still quite well separated as the delegate only knows what to reference, but this by itself means it has to know about something else outside it's world! That a method exists within another class!

Have I got myself it total muddle here, or is this a grey area, or is this actually down to interpretation (and if so, sorry as that will be off topic I'm sure). My question is, do delegates defy/muddy the OOP pattern?


Question: Defining a persistent static route on Mac OS X
Answer: Three approaches, in ascending order of goodness:


Manually create a launchd service to set up the route, as per http://osxfaq.com/tips/kluskens/index.ws
Use Lingon to automate the creation of a service, otherwise as above; this software is unmaintained, but still works fine as of OS X 10.5.8.
Use RouteSplit, a tool built for the purpose.