Put the knife down and take a green herb, dude.
One feller's views on the state of everyday computer science & its application (and now, OTHER STUFF) who isn't rich enough to shell out for www.myfreakinfirst-andlast-name.com
Using 89% of the same design the blog had in 2001.
FOR ENTERTAINMENT PURPOSES ONLY!!!
Back-up your data and, when you bike, always wear white.
MarkUpDown is the best Markdown editor for professionals on Windows 10.
It includes two-pane live preview, in-app uploads to imgur for image hosting, and MultiMarkdown table support.
Features you won't find anywhere else include...
You've wasted more than $15 of your time looking for a great Markdown editor.
Stop looking. MarkUpDown is the app you're looking for.
|Monday, March 08, 2004|
I've mentioned before that I recommend keeping debugging information around. At the same time, I'm not a big fan of code like the following at all.
strErrLocation = "before cmdTemp's second getCommand call"
cmdTemp = Me.getCommand(strSql)
strErrLocation = "after getCommand for long sql"
dreadParcelsAndFlags = cmdTemp.ExecuteReader
strErrLocation = "after long execute reader"
dsReturn = _
strErrLocation = "before dreadParcels disposal"
I'm not talking about the haphazard, stream-of-consciousness remarks describing location either, though those could be changed. What I dislike is that my IDE -- not a text editor, mind you, my *IDE*; I'd obviously forgive a text editor -- makes me put this sort of dscription inline with the rest of the code.
VS.NET is making strides with its ability to collapse blocks of comments with the click of a checkbox, but we could use a little more flexibility with the way the tools handle inline debugging information/error trapping code as well.
posted by ruffin at 3/08/2004 10:52:00 AM
All posts can be accessed here:
Just the last year o' posts: