This interesting article is seen on Monday, let me feel happy.
Does the C programmers really low-class (or say, high people first, etc.)? As a commonly used OO language, the support of C is less pitiful. In particular, the lack of automated refactoring tools and unit test IDE integration, making C almost impossible to be the preferred choice for XP team - or, make many C team miss out the opportunity to implement XP.
------------
Let's reconsider That
Aren't C Programmers People TOO?
By Michael Feathers
August 23, 2003
Summary
The Industry Needs Refactoring Tools for C . Now.
C programmers are people too, are not they? You would not think anyone thought so, the way the industry looks today. Java started its run in the late 90s and it rapidly became the lingua franca of programming. Over night, authors started using it for all of their examples in books and articles. Certainly this was response to the market, but Java is also a much more succinct language. If you are going to write about design, Java gives you a better chance of fitting a code snippet on a page. The net effect, however, is that if you look around for evidence of C 's continued existence, it is pretty easy to miss it. and, if you are one of these invisible C programmers and you are aware of that tools are Available for Java But Not C , WELL, You Should Be Screaming. C WAS My First Oo Language and Every Time I Go Back to Program in It i Notice The Lack of Support.
A few weeks ago, I was working with a team whose code is split right down the middle. Half of the code is Java and the other half is C . At the beginning of each iteration, the team members sign up for tasks. When someone walks into the room each morning you can pretty much tell whether they'll be working in C or Java. Their faces tell the story. The people who are going to be working in Java march in confidently and start up their Java-based IDE, then they go to get coffee while it loads (yes, there still are some issues in Java-land). When they get back with steaming cups in hand, they look around at the code, find the methods they need to change. They click a menu item and it shows them all of the places that send a particular message. Then they start going through the work of carving out a space to work with their code. They click the mouse around to extract interfaces and methods automatically so that they can Get Some Tests in Place for the Changes. The C Programmers Come in and bring up vi or emacs (they load quickly so no coffee for the C guys) then they browse around the code manually and start to figure out where to make their changes. Figuring out what uses what is often a blind-alley search. When they are ready to break some dependencies, they sit there and try to manually peel off interfaces by introducing virtual functions. They create new header files and extract methods by hand, all the while hoping and praying that they are not breaking anything. Without An Automated Tool To Check Their Refactorings It Is A Nerve-Wearing Process And IT '
s also several times slower. They know that the Java code is getting better, but it is hard to feel the progress on the C side. I do not think the lack of coffee has anything to do with it.Occasionally, some C teams I visit do not know what refactoring tools are out there. I was showing a team a testing technique a while back. The technique was language independent, so I pulled up a Java IDE. Over the course of my coding I found a method name That I Didn't Like. I Pulled Down A Menu and Hit Rename. When I Typed in The New Name It Was Replaced Every Place It Was Used. NOT EVERY PLACE IN THE, EVERY PLACE IT WAS USED. Three of the Team Members Recognized What The Saw When I Did IT and The Shouted "Nnnooo Waaaaayyy !!!" i think I could Have Induced DEAD FAINTS IW I'D SHOWN An Automated Extract Method Refactoring.
The Sad Thing IS, IT Shouldn't Be Like this.
The first research into automated OO refactoring was done by Bill Opdyke and Ralph Johnson in the early 1990s, in C . After that, John Brant and Don Roberts developed the first Smalltalk refactoring browser. Later, Martin Fowler wrote the book 'Refactoring.' That book and Extreme Programming really put refactoring on the radar screen. Java vendors scrambled to build refactoring tools into their IDEs. After all, it was the lingua franca, the language everyone is using, right?
