Tue Nov 7 08:22:46 PST 2006 Simon Marlow [EMAIL PROTECTED]
* fix line-comment syntax to not consider '--:' as a comment
See LineCommentSyntax on the wiki, ticket #42
M ./report/syntax-lexical.verb -1 +1
___
Haskell-prime mailing list
Hello John,
Friday, February 03, 2006, 3:39:38 AM, you wrote:
Got a unicode-compliant compiler?
JM sure do :)
JM but it currently doesn't recognize any unicode characters as possible
JM operators.
are you read this? :)
Log:
Add support for UTF-8 source files
GHC finally has
On 03 February 2006 00:40, John Meacham wrote:
On Thu, Feb 02, 2006 at 06:19:43PM -0600, Taral wrote:
Got a unicode-compliant compiler?
sure do :)
but it currently doesn't recognize any unicode characters as possible
operators. which it should, but I am just not sure how to specify that
On 03 February 2006 04:07, Taral wrote:
On 2/2/06, John Meacham [EMAIL PROTECTED] wrote:
but it currently doesn't recognize any unicode characters as possible
operators. which it should, but I am just not sure how to specify
that yet until some sort of standard develops. Once there are more
significantly worse error messages?
My point here was not that the error messages was that terrible. I just wanted to point out to Manuel that it does happen that single line comments start with a symbol. Which makes the current comment syntax somewhat awkward.
Cheers,/Josef
Hello Manuel,
Thursday, February 02, 2006, 3:40:26 AM, you wrote:
MMTC I am against such a change. The change would break existing software
MMTC (eg, Yampa) and secondly I don't buy the main sources of
MMTC confusion for beginners argument. The confusion arises only when a
MMTC single line
Am Montag, 30. Januar 2006 17:24 schrieb Taral:
On 1/30/06, Thomas Davie [EMAIL PROTECTED] wrote:
It gives you regexp and nothing more - this makes it a pain in the
arse to input every possible character that is/isn't allowed.
Steal it from places (vim):
syn match hsLineComment
On 2/2/06, Wolfgang Jeltsch [EMAIL PROTECTED] wrote:
Am Montag, 30. Januar 2006 17:24 schrieb Taral:
On 1/30/06, Thomas Davie [EMAIL PROTECTED] wrote:
It gives you regexp and nothing more - this makes it a pain in the
arse to input every possible character that is/isn't allowed.
Steal
On Thu, Feb 02, 2006 at 06:19:43PM -0600, Taral wrote:
Got a unicode-compliant compiler?
sure do :)
but it currently doesn't recognize any unicode characters as possible
operators. which it should, but I am just not sure how to specify that
yet until some sort of standard develops. Once there
On 2/2/06, John Meacham [EMAIL PROTECTED] wrote:
but it currently doesn't recognize any unicode characters as possible
operators. which it should, but I am just not sure how to specify that
yet until some sort of standard develops. Once there are more unicode
compliant compilers out there
munch. I know there are plenty of people who agree with you. But there are those that agree with my standpoint as well. I'm not going to propose that we start arguing about this. I suppose we'll have to use other arguments to persuade each other about the comment syntax.
/Josef
Hi all,
To corroborate Wadler's law further.
Josef wrote:
Oh yes, it does happen that a single line comment begins with a
special symbol. It has happened to me on several occations when using
haddock annotation to my source code. It is all to easy to forget that
extra space. With
On Thu, 2 Feb 2006, Henrik Nilsson wrote:
Hi all,
To corroborate Wadler's law further.
Josef wrote:
Oh yes, it does happen that a single line comment begins with a
special symbol. It has happened to me on several occations when using
haddock annotation to my source code. It is
On 30 Jan 2006, at 14:49, [EMAIL PROTECTED] wrote:
Quoting Thomas Davie [EMAIL PROTECTED]:
On 30 Jan 2006, at 14:28, Neil Mitchell wrote:
Another argument in favour of this is that most editors with
syntax
hilighting will show -- as a comment, which again increases the
confusion factor.
Quoting Thomas Davie [EMAIL PROTECTED]:
I agree, this is not a great argument, but the fact that the language
is inconsistent, and that it confuses people easily, and can't come
up with great error messages when it does go wrong, (my original
arguments) really are good arguments for fixing
15 matches
Mail list logo
