The Artima Developer Community
Sponsored Link

Agile Buzz Forum
Feel the simplicity

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
James Robertson

Posts: 29924
Nickname: jarober61
Registered: Jun, 2003

David Buck, Smalltalker at large
Feel the simplicity Posted: Sep 20, 2004 2:32 AM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by James Robertson.
Original Post: Feel the simplicity
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Latest Agile Buzz Posts
Latest Agile Buzz Posts by James Robertson
Latest Posts From Cincom Smalltalk Blog - Smalltalk with Rants

Advertisement

Have a look at this post on debugging in Mono. I like this part:

What was missing was an easy way to get data out of a debugging session. By easy I mean right here, right now, that @$#^ ASN.1 blob looks wrong. It's too late to modify the code, it's too big to be decoded by hand (or it's also to late to do so ;-).

So something easy would be writing an assembly consisting of a single class with a single method to interpret the data, compiling it and, without even restarting the IDE, using the new code as an help to debug the current problem.

We're not there yet but we're getting close!

Actually with Visual Studio .NET 2005 the step are:

  1. Create a new assembly, referencing the debugging assembly;
  2. Implement this single method, Show, in a class implementing IDebugVisualizer;
  3. Add an assembly-level attribute, DebuggerVisualizer, to map the debugging extension with a type;
  4. Compile the assembly *;
  5. Copy the assembly to a pre-determined location (which can be automated with the compile step);
  6. and use it without restarting Visual Studio!

And in Smalltalk, the one step is:

Create a #printOn: method in the class(es) in question - including the ability to override system classes if they aren't descriptive enough. And obtw - you can do that while the debugger is looking at the code, and have it change right then. I love the way MS and Java folks keep finding incredibly complex ways to not quite match the power of Smalltalk.

The developer in question said he hoped he'd see this in other IDE's soon - here's where to look.

Read: Feel the simplicity

Topic: Huh? Previous Topic   Next Topic Topic: Agile Delphi...

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use