Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Proof in the pudding

Sorry, I couldn't resist. :^)
 
 The principal trouble with the proof is in the pudding is that it makes no sense. What has happened is that writers half-remember the proverb as the proof of the pudding, which is also unintelligible unless you know the full form from which the tag was taken, and have modified it in various ways in unsuccessful attempts to turn it into something sensible.
[...]
The full proverb is indeed the proof of the pudding is in the eating and proof has the sense of “test” (as it also has, or used to have, in phrases such as proving-ground and printer’s proof). The proverb literally says that you won’t know whether food has been cooked properly until you try it. Or, putting it figuratively, don’t assume that something is in order or believe what you are told, but judge the matter by testing it; it’s much the same philosophy as in seeing is believing and actions speak louder than words.
 
 
 
 

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Friday, December 09, 2005 11:41 AM
To: CDT General developers list.
Subject: [cdt-dev] Proof in the pudding

Hey gang,

 

As I mentioned in the *DT bug report, I am playing with extending the CDT to do Ada. I spent a half an hour this morning setting things up and I was shocked at how much I got going.

 

Here are a couple of screenshots of the Editor and Debugger working with Ada. I am using gnatmake in Standard Build as my builder and created a Make Target to pass in the name of the Ada unit I wanted to build and the –g option for debug symbols.

 

http://cdt.eclipse.org/ada/AdaEdit.png

http://cdt.eclipse.org/ada/AdaDebug.png

I created the content types for Ada’s ads and adb files and hooked up the CEditor to those content types. Obviously the CEditor doesn’t know about Ada keywords and there’s no CModel populated for Ada things. But I don’t see this being too much work, and is something we need to do to properly support things like gcc specific keywords.

 

The biggest surprise was that breakpoints and the debugger just worked. A lot of this has to do with the multi-lang capabilities of gdb but also with the fact that the CDT’s debugger hasn’t forced language on the debug session, at least from what I can tell. Great work debug team!

 

Cheers,

Doug


Back to the top