Joachim Durchholz wrote:
> Just to complement Jon's view: I don't think there are any *serious*
> problems with recovering indented code from web pages or mail quotes.
> Just make sure that whitespace is properly handed through, that's all,
> and it's not even difficult. Hey, Evolution will even strip the angle
> brackets when copying from quoted mail ;-)
Ugh. I was bitten by this *again* yesterday, trying to cut and paste some
F#
code from a blog article and Windows removed all "\n"s. In the end I used
my Linux box to cut and paste into a text file that I loaded into the
Windows box using putty and then cut and pasted that (correctly formatted)
into Visual Studio...
> The argument for indentation is that you indent your code anyway, so why
> specify nesting with both keywords and indentation? That's just silly.
Turn autoindenting on!
> Besides, keywords eat vertical screen estate (if only for the closing
> brace or the "end" keyword), and that's a real restriction: the more
> code you can see on a screenful, the easier it is to put its
> constituents into proper perspective.
True. I think the IDE should compact those keywords though. Same goes
for "+." in OCaml, which should by typeset as "+" in an IDE.
> Coding does get noticeably faster
> if you can see more relevant text at a glance (in the time of 24x80
> displays, I once got access to a laser printer that could print 200
> lines per page in landscape mode; on fanfold paper, that meant a
> whopping 400 lines at a glance, and enabled me to analyze the code in a
> speed that would have been plain impossible otherwise. I'll trade more
> lines per page for almost everything else... though I do appreciate the
> occasional blank line to structure the code ;-) )
> Of course that's just anecdotal, but anyway.
You're mad. :-)
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?u
|
