|
![](/i/fill.gif) |
Darren New <dne### [at] san rr com> wrote:
> > I'm not concerned about typos. I'm concerned about whitespaces being lost
> > in transfer
> Well, don't do that. :-) Treat python source code as something other than
> prose, and you won't have that problem.
Too bad that online forums and blogs won't.
> Really, if you're not using unicode, you're already behind the ball. So if
> your transfer mechanism can't handle whitespace, you shouldn't be using it
> to ship code around.
Tell that to all the forum and blog software out there.
> > Because when your editor can autoindent your code, it makes programming
> > enormously easier (similarly to how syntax highlighting does).
> Python editors auto-indent code. I'm not sure what you mean. An indent
> always follows a line ending with a colon, and the dedent is no harder than
> your closing brace in C.
Autoindentation is impossible for a program to do because it cannot know
where the block should end, as there is no keyword/character ending the block.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |