[Haskell] Re: Use of tab characters in indentation-sensitive code

2004-01-25 Thread Sean L. Palmer
] To: Sean L. Palmer [EMAIL PROTECTED] Cc: Wolfgang Thaller [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, January 25, 2004 1:06 PM Subject: Re: Use of tab characters in indentation-sensitive code Sean L. Palmer [EMAIL PROTECTED] writes: Why has HTML been out for many many years, and yet

Re: Use of tab characters in indentation-sensitive code

2004-01-24 Thread Sean L. Palmer
Why has HTML been out for many many years, and yet programming languages still use plain ASCII text exclusively? Don't we have similar needs as other electronic document manipulators? Someone should decide on a subset of HTML that is intended for programming. Then we could use *actual*

Re: Haskell naming conventions

2003-12-27 Thread Sean L. Palmer
That was quite a satisfying explanation, thank you. That is certainly clearing a few things up. Sean - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, December 26, 2003 3:07 AM Subject: Re: Haskell naming conventions G'day all. Quoting Lennart

Haskell naming conventions

2003-12-23 Thread Sean L. Palmer
It occurs to me that Haskell would be quite a bit easier for OO and traditional programmers to grasp if Haskell would actually use the correct, or at least more commonly used, names for things. For instance, data Maybe a = Nothing | Just a Maybe is a type constructor and Nothing and Just

Re: literate comments

2003-10-28 Thread Sean L. Palmer
You could make a utility that just strips code out of XML, using the XML nesting as indentation for the Haskell code. Run it as a preprocessor. It's hard to get stuff like that standardized though. I imagine any kind of development environment is free to pretty up or package the source however

Re: lexer puzzle

2003-09-25 Thread Sean L. Palmer
A... should be split into A.. and . I found a compromise: let's make it a lexing error! :-) At least that agrees with what some Haskell compilers implement. No current Haskell compiler/interpreter agrees with what the report seems to say, that is that A... should be lexed as the two tokens