Alastair David Reid wrote:
[...]
What does the language definition say about [tabs]?
[...]
The Haskell 1.4 report says what is meant to happen (section 1.5)
(which was to follow the convention).
The Haskell 98 report omits this section.
I would like to report this omission as a bug in
Brian Boutel wrote:
Sigbjorn Finne wrote:
What does the language definition say about this?
Nothing at all, I believe, but the convention is for tab characters
to be interpreted by an output device as moving the cursor to
the next tab stop/alignment column. In the absence of any
Sigbjorn Finne wrote:
What does the language definition say about this?
Nothing at all, I believe, but the convention is for tab characters
to be interpreted by an output device as moving the cursor to
the next tab stop/alignment column. In the absence of any custom
set of tab stops,
Rijk-Jan van [EMAIL PROTECTED] writes:
Recently, Craig Delehanty discovered that there is
a difference in behaviour of putStr a\tb between
Hugs and WinHugs (see comp.lang.functional).
Hugs interprets it as a alignment character:
putStr a\tb
a b
(7 spaces)
but in WinHugs, it
Rijk-Jan van Haaften [EMAIL PROTECTED]:
What does the language definition say about [tabs]?
Sigbjorn:
Nothing at all, I believe, but the convention is [...]
The Haskell 1.4 report says what is meant to happen (section 1.5)
(which was to follow the convention).
The Haskell 98 report omits
Hello,
Recently, Craig Delehanty discovered that there is
a difference in behaviour of putStr a\tb between
Hugs and WinHugs (see comp.lang.functional).
Hugs interprets it as a alignment character:
putStr a\tb
a b
(7 spaces)
but in WinHugs, it is always the same as 8 spaces:
putStr
