Alex,
| Ok, I'm game to default to haskell98 in the presence of ambiguity, but
| in most cases the extension involves new syntax and that should be enough.
Trying to compile the program both ways (or 2^n ways) to check for ambiguity
sounds like a pretty heavy hammer to crack this nut.
GHC is
| Nice feature but feel like a band-aid. In particular it makes SYB style
| programming more difficult because field labels aren't types.
|
| Almost every other record syntax plan involves field labels as types so
| you can do interesting type dispatch.
Record systems are indeed an interesting
Wolfgang Jeltsch [EMAIL PROTECTED] writes:
It made me discover that I use more language extensions than I thought I was
using.
I think, it’s a good thing if you have to be clear about what extensions you
use and what you don’t use. What if someone wants to compile your code with
a
Simon Peyton-Jones wrote:
| Nice feature but feel like a band-aid. In particular it makes SYB style
| programming more difficult because field labels aren't types.
|
| Almost every other record syntax plan involves field labels as types so
| you can do interesting type dispatch.
Record systems
Yitzchak Gale wrote:
Quoth InteractiveUI.runGHCi:
case maybe_expr of
Nothing -
do
#if defined(mingw32_HOST_OS)
-- The win32 Console API mutates the first character of
-- type-ahead when reading from it in a non-buffered manner. Work
--
Alex Jacobson wrote:
Isn't use of the extensions detectable by the compiler?
Not always, no. Some extensions modify the syntax, such that programs
accepted with the extension turned on are not necessarily a superset of
those accepted with the extension turned off. For example: MagicHash
Alex Jacobson wrote:
In any case, I'm pretty sure the correct answer is not 50 language
pragmas with arbitrary spellings for various language features at the
top of each source file.
You probably won't like any of these, but there are many ways to avoid
writing out all the pragmas at the
Or use a preprocessor that inserts a LANGUAGE pragma. :)
On Nov 22, 2007 9:14 AM, Simon Marlow [EMAIL PROTECTED] wrote:
Alex Jacobson wrote:
In any case, I'm pretty sure the correct answer is not 50 language
pragmas with arbitrary spellings for various language features at the
top of
Hi all,
It is now possible to register a new user account for yourself on the
GHC trac. To do so, make sure you are logged out and then click the
register link at the top-right, or go to this URL:
http://hackage.haskell.org/trac/ghc/register
Making your own account preferred over using the
That's good news. It also means you can set your own preferences (if
you did so with the guest account you ended up receiving mails related
to ticket you didn't create)
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
A pre-processor is a great idea. Template Haskell and Cabal make it
possible to extend the language by adding all kinds of funky
pre-processing (via Cabal hooks) and compile-time calculations. It
wouldn't be too difficult to add a package-specific .ehs file type with
the desired behavior.
Sigbjorn wrote:
This was a hack to work around similar behaviour when starting up GHCi,
Notice that my workaround is only applied upon startup, not in the REPL. =
floating the hackery inward could just save the day.
OK.
Simon Marlow wrote:
The underlying bug is in the Windows CRT, or
Hi all,
Overlapped IO support for files and sockets is now in place in my test
version of ghc-head. File functions use the win32 api and large files
and Unicode filenames are supported (i'm not sure if ghc currently
supports that for Windows).
I've addded a new type Hdl which is an alias for FD
It seems like use of a lot of extensions is so obvious from syntax that
the compiler is able to suggest the correct pragma to turn on to enable
that syntax. In fact the way I know to use most of these pragmas is
because the compiler told me about them.
So, my suggestion is that in any case
| So, my suggestion is that in any case where the compiler currently
| suggests use of a particular pragma in an error message, it should
| instead turn that pragma on and produce a warning.
In the cases where the compiler makes that suggestion, yes what you suggest
would be feasible I think.
I had the same problem on OS X with Safari. The solution was to
delete the old username/password that Safari had saved in OS X's
Keychain Access utility. I imagine there's a similar solution for
other browsers/OSes.
Hope that helps,
-Judah
On Nov 22, 2007 10:41 AM, Deborah Goldsmith [EMAIL
I stupidly missed the make sure you are logged out part, and now I
can't log in to the account I created. :-/ Any suggestions? When I log
in it just logs me in as guest without any interaction.
Deborah
On Nov 22, 2007, at 3:38 AM, Ian Lynagh wrote:
Hi all,
It is now possible to register
Ahh, that fixed it. Thanks!
Deborah
On Nov 22, 2007, at 11:31 AM, Judah Jacobson wrote:
I had the same problem on OS X with Safari. The solution was to
delete the old username/password that Safari had saved in OS X's
Keychain Access utility. I imagine there's a similar solution for
other
Am Mittwoch, 21. November 2007 19:38 schrieb Alex Jacobson:
Isn't use of the extensions detectable by the compiler?
So you want extension inference. ;-)
[…]
In any case, I'm pretty sure the correct answer is not 50 language
pragmas with arbitrary spellings for various language features at
Am Donnerstag, 22. November 2007 02:07 schrieb Alex Jacobson:
Duncan Coutts wrote:
On Wed, 2007-11-21 at 19:26 -0500, Alex Jacobson wrote:
Ok, I'm game to default to haskell98 in the presence of ambiguity, but
in most cases the extension involves new syntax and that should be
enough.
On Fri, 2007-11-23 at 01:50 +0100, Wolfgang Jeltsch wrote:
Dont’t just think in terms of single modules. If I have a Cabal package, I
can declare used extensions in the Cabal file. A user can decide not to
start building at all if he/she sees that the package uses an extension
21 matches
Mail list logo
