Public schooled

Returning to the world of statically typed languages, I am reminded of how weak the public access specifier is from an architectural perspective. Private is fine. Internal is fine. But public is a nightmare. Public in what context, or rather, public to what other assemblies?

Assemblies and their connectivity is a topic that I studied in graduate school but haven't thought of in a while. Like any important topic, however, it's coming up again. In any software project of reasonable size, there are certain assemblies that should not reference any part of one another in order to ensure the manageability of the system as a whole.

Such references will not cause compile time errors because they do not cause a conflict in the traditional sense of the word. The result is an architectural conflict rather than a computation conflict. And I know of no mechanisms that have filtered down from the research community to make such references rain warnings down upon anyone who would try to make them.

Gar.

In Europe, brown people own the Internet Cafés

Barcelona is damp and humid, smelling of rain and sweat. It´s 4:30 in the morning to my body and I´m dragging everything I need over the next ten days around train stations, airports, and bus terminals. For the type of area that usually exists around a bus station, this is actually quite nice. I think I can find a decent breakfast among what is open on a deserted Good Friday.