On 18 Jun 2015, at 12:12 PM, Dave <[email protected]> wrote:
> It amazes me that XCode still actually puts formatting information in the
> file itself, IMO, it would be better to store source files with no white
> space and reformat it as per the users preferences when they open the file.
> That way, we could all views comments and format it how we like to see it.
> For instance, some people like the K&R Style and some don’t, some like to
> indent code, some don’t.
My crotchets are at least as good as yours:
• When I see a line in my own code that is hard to read because it is wider
than a typical editor, I take it as as sign that I should break it myself. I
also ask myself whether I’ve organized the logic properly. Maybe yes, maybe no,
but it’s a smell, like a 500-line function. That answers objections to
automatically wrapping code, that I can think of: It’s objectionable because it
doesn’t reflect your intentions. Formatting code so it reflects your intentions
is your problem.
• I constantly revise my documentation comments. (In others, a sign of
meticulousness, I’m just compulsive.) Hard-wrapped lines get longer and
shorter, and then I must either re-wrap by hand, or tolerate lines that run off
the right edge, or are small enough to falsely suggest a paragraph break. (In
others, a sign of refined sensitivity to information design, but I’m just
compulsive. ASD is endemic to this profession.) Paragraphs should be paragraphs.
And I’ve given up on trusting documentation generators’ treatment of paragraph
breaks.
> This is how Think Pascal worked IIRC (was a *long* time ago!).
Yes, you could do it on a 1 MHz 68000 in ~300K available RAM and ~100K free
storage, with (apparently) a proprietary compressed parse tree. For _Pascal,_
canonically in single compilation units. (UCSD p-System [Apple Pascal and the
Lisa-based tools] had a module-import statement, but I think it was an
extension.)
All the grammar you’d need fits in the generous layout of a poster on my
bedroom wall. THINK Pascal was before Object Pascal, MacApp, and MPW; good
luck on a stable parse-tree file format for those, much less ObjC/C++/Swift
plus semantic coloring and cross-unit dependencies.
Jens:
> That’s a major reason why almost no one has ever used anything but
> human-readable plain text for source files.
Prograph! Helix! APL! COME HOME! ALL IS FORGIVEN!!
— F
--
Xcode 6 Start to Finish
Really. Date 7, marry App Store & general-release distributions in 6.
And probably the last edition, so you can make a fortune on eBay in a few years.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com
This email sent to [email protected]
