Languages and Splitting the Interface from Implementation

Hopefully a rare event, but I need to rant a little. After looking through C# code that isn't my own today I'm longing for a language that splits the interface from the implementation details. It isn't that the code is bad, it's that there's a good bit of it and I'm not used to working in a language that doesn't split the interface from the implementation. I'm far more comfortable looking through Pascal Interface and Implementation sections and Objective-C/C/C++ header files and implementation files. Lately I've seen a lot of criticism of that as "old" because newer languages don't use it at all, but I have to say when you come to a significant amount of code you didn't write from a person whose style you're not familiar with, it helps. I'll have to reinstall ModelMaker Code Explorer. For some reason it's not available in Vistual Studio any longer. I must have removed it at some point, but this is killing me and turning on code folding isn't helping... In fact, perhaps I'll just import everything into ModelMaker itself. Perhaps people feel separate interface sections are redundant because they use UML tools like that instead. Don't know, but it's very similar I suppose. I've come to like C#, I really have. Coming from Delphi it feels very natural, particularly since the same man had a heavy hand in both. But I really miss interface sections and header files when I work in it. Okay, I think I'm done ranting now...


About The Author

Ron Grove draws on over ten years of training, network administration and development experience. He loves to work with new technology and see how that technology can be best utilized by his clients. You can find him through his company Evanoah, LLC and his LinkedIn profile is here.