Re: [Haskell] Making Haskell more open
Well, I in no ways am an expert, but AFAIK the system is PHP/SQL based, therefore I don't think it should be very hard to modify the upload/download system to include PDF or files of any other form for that matter. On 11/11/05, Till Mossakowski [EMAIL PROTECTED] wrote: I have also made nice experiences with MediaWiki/WikiPedia.However, I think while you can include images on MediaWiki pages, you cannot include documents (like ps or pdf) - these have to beexternal links. Of course, the possibility of including such documentswould be a desirable feature for a system of Haskell documentationpages. Perhaps it is not too difficult to add this feature for a MediaWiki expert?Till MossakowskiAndrea Sassanelli wrote: Sorry to intrude myslf like this in the conversation. First of all, let me present myself: My name is Andrea Sassanelli, and I'm Italian. I have just started studying Haskell at the UoEdinburgh this year, and immediatelly fell in love with it. On a sidenote, the wikipedia does rely on moderators who review the changes, but common users are able to undo changes as well, and can therefore bring a maliciously messed up page back to it's origiinal state. Basically MediaWiki/WikiPedia rely on the assumption that there are more good folk than bad folk, and this (IMHO) should be even more true in the case of a relatvelly medium/small-scale thing like the Haskell Documentation (small compared to a whole encyclopedia, i mean). Open documentation like this is definitelly a good idea to make the language docs not only more accessible, but also more user-friendly, and would surely give a positive image to the community as a whole. I unfortunatelly am not suted (?yet?) to work on any usefull documentation, as I am a novice, but I think the system would work. Andrea Sassanelli ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell--Till Mossakowski Phone +49-421-218-4683Dept. of Computer ScienceFax +49-421-218-3054University of Bremen [EMAIL PROTECTED]P.O.Box 330440, D-28334 Bremen http://www.tzi.de/~till ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
[Haskell] CFP: European Conference on Logics in AI [JELIA'06]
+---+ | * CALL FOR PAPERS * | | ** JELIA'06** | | --- | | 10th European Conference on Logics in Artificial Intelligence | | Liverpool, U.K., September 13-15, 2006| | http://www.csc.liv.ac.uk/~jelia | | | | Submission deadline: 1st May 2006 | +---+ JELIA'06 will bring together researchers interested in all aspects concerning the use of logics in AI to discuss current research, results, problems and applications of both a theoretical and practical nature. Authors are invited to submit papers presenting original and unpublished research in all areas related to the use of Logics in AI. Proceedings will be published by Springer-Verlag in the Lecture Notes on Artificial Intelligence series. All submissions must be received (in PS or PDF only) by 1st May, 2006, and should be submitted via the form available at the JELIA-06 web page. Papers should be written in English, and should be formatted according to the Springer LNCS style (with standard margins). There are two categories of submission: A. Regular papers. Submissions should not exceed 13 pages including figures, references, etc., and should contain original research, and sufficient detail to assess the merits and relevance of the contribution. B. Tool descriptions. Submissions should not exceed 4 pages, and should describe the implemented tool and its novel features. A demonstration is expected to accompany a tool presentation. IMPORTANT DATES Deadline for submission: 1st May, 2006 Notification of acceptance: 8th June, 2006 Camera Ready Copy: 26th June, 2006 For further details, including lists of Conference Officials and Programme Committee, see http://www.csc.liv.ac.uk/~jelia Send your questions and comments to [EMAIL PROTECTED] This message was sent using IMP, the Internet Messaging Program. ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
[Haskell] ICALP 2006 -- Call For Workshop Proposals
* Apologies for multiple copies * 33rd International Colloquium on Automata, Languages and Programming ICALP 2006 S. Servolo, Venice - Italy Call for Affiliated Workshops Conference Dates: July 10-14, 2006 Affiliated Workshop Dates: July 9, 15, and 16, 2006 Researchers and practitioners are invited to submit proposals for workshops on topics related the conference tracks, namely: Algorithms, Automata, Complexity and Games (track A); Logic, Semantics, and Theory of Programming (track B); and Security and Cryptography Foundations (special track C). The purpose of the workshops is to provide participants a forum for presenting novel ideas and for discussing in a small and interactive atmosphere. The main responsibility of organising a workshop goes to the chairperson of the workshop.The format of each workshop is determined by its organisers. The workshop proposals will be selected by the ICALP organization, under advice of the ICALP PC chairs and EATCS. Proposals should include: * Name and duration (from half a day to two days) of the proposed workshop. * A short scientific summary of the topic, including a discussion on the relation with the ICALP topics. * A description of past versions of the workshop, including dates, organisers, submission and acceptance counts, attendance. * Procedures for selecting participants and papers, and expected number of participants. * Plans for dissemination (for example, published proceedings or special issues of journals). IMPORTANT DATES: November 27, 2005: Deadline for submitting workshop proposals December 16, 2005: Notification of acceptance Workshop proposals must be submitted in plain text, PDF or Postscript format by e-mail to [EMAIL PROTECTED] For further information consult the ICALP 2006 web site: http://icalp06.dsi.unive.it/ or contact the ICALP 2006 Workshops Chairs: - Andrea Pietracaprina [EMAIL PROTECTED] - Francesco Ranzato [EMAIL PROTECTED] - Sabina Rossi [EMAIL PROTECTED] ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] [ANNOUNCE] yhc - York Haskell Compiler
Is there some trick to getting it to build ? I've never used the Makefile, but it should work as is! One way to build it, the way I use is: $ cd /root/projects/haskell/yhc/src/compiler98 $ ghc --make -cpp Main -o yhc Thanks Neil ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Re: Making Haskell more open
Not that I have any emotional attachment to MoinMoin, which the hawiki is based on, but... Ashley Yakeley wrote: I would much prefer to use a MediaWiki than the existing hawiki. Particularly valuable are the elimination of RunTogetherWordLinks and the separation of article and talk spaces. MoinMoin supports arbitrarily named links, like so: [anything goes]. If you set the appropriate check mark in your user preferences, RunTogetherWords are displayed as Seperate Word for you. Seperation of article and discussion is a cultural, not a technical problem. Till Mossakowski wrote: However, I think while you can include images on MediaWiki pages, you cannot include documents (like ps or pdf) MoinMoin supports arbitrary attachments. Just put a link named attachment:filename into the page, then follow the new link to upload the attachment. If it is an image, it will even be displayed inline. However, this feature is currently disabled. (Why?) What HaWiki needs is not yet another wiki engine (unless one were written in Haskell, of course :)), but better indices. There are too few ways to get around (I'm always using the search features, but those should be the last resort, not the first option) and too many orphaned pages. Udo. -- A man always needs to remember one thing about a beautiful woman: Somewhere, somebody's tired of her. signature.asc Description: Digital signature ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] [ANNOUNCE] yhc - York Haskell Compiler
Just so that people don't get the wrong idea ... - Yhc is a working title and it's still not totally decided what it's relation to nhc98 is. It may be merged back into nhc98, it may replace nhc98 or it may end up as an entirely seperate project from it. - It's very much work in progress, indeed the source code in the darcs repository as of today is currently somewhat disfunctional as is in between changes (hence why the Makefile is broken). - It's just an experiment of mine with the backend that turns out to have sparked some interest. It seems to compile most of Haskell 98 (at least it did when it last worked ;-)) but it's in no way an industrial strength compiler yet. - It's just me and a few other students (who are or were recently at York) working part time. It's in no way an official release. That said people are free to have a play around and comments, suggestions or ports are all welcome. I'll try and get the code in darcs to a reasonable state ASAHP. Hope that helps settle any confusions :-) Tom Shackell On 11/11/05, Thomas Davie [EMAIL PROTECTED] wrote: Announcing the York Haskell Compiler - a Haskell 98 compiler with roots in nhc98. It's not totally finished, but is getting there quickly, and could well be of interest to Haskell developers. Webpage: http://www-users.cs.york.ac.uk/~ndm/yhc/ Project Blog: http://yhc06.blogspot.com/ Project Wiki: http://haskell.org/hawiki/Yhc Darcs: darcs get http://www.cs.york.ac.uk/fp/darcs/yhc As many of you now know, the York Haskell Compiler project is now getting well and truely off the ground. For those of you that don't know, I'll give you a quick summary. Over the last few months Tom Shackell has rewritten the back end of nhc98, to create the yhc compiler. The new compiler is extremely lightweight, runs fast, and generates code that runs at a speed roughly midway between hugs and ghc. Better than that though, the compiler generates bytecode to be run on a virtual machine, and thus can create portable binaries! The virtual machine is written in C and thus can bootstrap the whole compiler system on just about any platform (it's already known to work on linux, windows and OS X). Several problems that nhc had have been addressed in the rewrite including the hi-mem bug, and making it work on Windows (without cygwin). There is still a lot of work to do though - contributions welcome! Thanks Tom Davie (and the rest of the yhc team) ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] [ANNOUNCE] yhc - York Haskell Compiler
On Fri, Nov 11, 2005 at 12:24:49PM +, Neil Mitchell wrote: - It's very much work in progress, indeed the source code in the darcs repository as of today is currently somewhat disfunctional as is in between changes (hence why the Makefile is broken). It may be a good idea to have yhc-stable and yhc-devel repositories, where yhc-stable should be functional most of the time. That's how darcs' repos are organized. Best regards Tomasz ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
Am Donnerstag, 10. November 2005 12:27 schrieb Simon Peyton-Jones: [...] - Work is afoot to move GHC's source-code repository to Darcs, to make it easier for people to contribute patches Is it planned to split the current big monolithic repository into multiple repositories in conjunction with doing the CVS-to-darcs transition? I'd strongly recommend this. What do others think? [...] * The GHC user manual [currently generated using DocBook] I think it should continue to be written in DocBook. (It should switch to DocBook XML if it's still using SGML DocBook.) XML documents are type-safe in contrast to LaTeX documents, for example. XML is well supported. DocBook stresses logical markup and allows very specific markup and therefore supports conversion into different formats (HTML, PDF, ...) very well. Again, what do others think? [...] Does anyone have experience of a larger-scale Wiki like this? (A few people have mentioned MediaWiki to me [MW], but I know nothing about it.) MediaWiki is the software behind Wikipedia [1] so it should be well suited for large wikis. :-) In addition, I like the fact that with MediaWiki you can give articles nice names and use alternative names in link texts so you aren't forced to write sentences like: You can solve this problem with MultiParameterTypeClasses. but you can write correct English sentences like: You can solve this problem with multi-parameter type classes. How would we make sure it stayed organised? And avoid getting screwed up by malicious folk? At Wikipedia, you can log in and modify content and you can modify content while not being logged in. In the first case, the history mentions your username, in the second case, it mentions your IP address. I think, MediaWiki can be configured so that only logged-in users are able to do modifications. As far as I can remember, I once saw a site using MediaWiki, which didn't allow modifications from non-registered users. But honestly, would we need to protect ourselfs from malicious folk? At Wikipedia, they have problem with malicious people at a couple of articles, so they sometimes have to lock articles. (This tells us that article locking obviously is another feature of WikiMedia. As far as I know, this kind of locking can be done by different persons, not just one super user.) But who would want to screw up pages about Haskell? I could imagine that making the Haskell Website a wiki is a really good idea. At least, Wikipedia shows how much of high-quality content can evolve out of a wiki project. [...] Simon Best wishes, Wolfgang [1] http://www.wikipedia.org/ ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] [ANNOUNCE] yhc - York Haskell Compiler
Yes that's a good idea, I would have tidied things up somewhat if I'd known it was going to be announced on the mailing list :-) Cheers Tom Tomasz Zielonka wrote: On Fri, Nov 11, 2005 at 12:24:49PM +, Neil Mitchell wrote: - It's very much work in progress, indeed the source code in the darcs repository as of today is currently somewhat disfunctional as is in between changes (hence why the Makefile is broken). It may be a good idea to have yhc-stable and yhc-devel repositories, where yhc-stable should be functional most of the time. That's how darcs' repos are organized. Best regards Tomasz ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Re: Making Haskell more open
Am Donnerstag, 10. November 2005 19:57 schrieb Ben Moseley: Simon Peyton-Jones simonpj at microsoft.com writes: ... And avoid getting screwed up by malicious folk? Probably the biggest example of this type of thing working well on a large scale is Wikipedia. I'm not intimately familiar with the process they use, but I believe there are a number of people who regularly review all the Recent Changes and undertake to 'undo' any malicious/inaccurate modifications. I cannot imagine that a couple of people is sufficient to review all recent changes and therefore I don't think they do it this way. There are some typical articles where screwing up happens often, so these articles might be regularily revisited. Screwing up of articles might as well be removed by ordinary people who discover ugly things in articles by accident. [...] Best wishes, Wolfgang ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Re: Making Haskell more open
Am Freitag, 11. November 2005 12:22 schrieb Udo Stenzel: Seperation of article and discussion is a cultural, not a technical problem. One thing I always disliked about the Haskell Wiki is that you often have a short article and then a lot of user comments. What people searching for information on a certain topic mostly want is a consistent article describing the topic, not a text with a mix of pieces certain users threw in. [...] What HaWiki needs is not yet another wiki engine I think, the discussion was not about basing the HaWiki on a different wiki engine but to create a new wiki which should be a replacement for the whole Haskell website. [...] Udo. Best wishes, Wolfgang ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
[Haskell] Making Haskell more open
Simon Peyton-Jones simonpj at microsoft.com writes: The important thing is that these mechanisms should work without any central intervention. These are just two suggestions. Perhaps there are other such mechanisms that we could put in place. Ideas? One thing I have missed ever since I first visited haskell.org is a web forum. I guess most of the people reading/posting on the mailinglists are used to it and like it, but I prefer forums. Actually, I have never posted here before, but I usually read the (for me) intresting parts from the Haskell Archives. However, I have not read a forum-discussion yet, and since noone has proposed it I felt that I should do a post about it. /vb ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
RE: [Haskell] Making Haskell more open
On 11 November 2005 12:57, Wolfgang Jeltsch wrote: Am Donnerstag, 10. November 2005 12:27 schrieb Simon Peyton-Jones: [...] - Work is afoot to move GHC's source-code repository to Darcs, to make it easier for people to contribute patches Is it planned to split the current big monolithic repository into multiple repositories in conjunction with doing the CVS-to-darcs transition? I'd strongly recommend this. What do others think? We do plan to split the repository into several chunks, and over time some of the libraries will migrate into their own repositories. Here is the current plan: http://www.haskell.org//pipermail/cvs-ghc/2005-November/027174.html [...] * The GHC user manual [currently generated using DocBook] I think it should continue to be written in DocBook. (It should switch to DocBook XML if it's still using SGML DocBook.) XML documents are type-safe in contrast to LaTeX documents, for example. XML is well supported. DocBook stresses logical markup and allows very specific markup and therefore supports conversion into different formats (HTML, PDF, ...) very well. Again, what do others think? We already use DocBook XML, and I'm relatively pleased with it, except for the fact that it's far from easy to set up a working DocBook toolchain on your system unless your OS of choice is up to date and has a well-maintained set of DocBook packages. Cheers, Simon ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
On Fri, 2005-11-11 at 15:49 +0100, Victor Blomqvist wrote: Simon Peyton-Jones simonpj at microsoft.com writes: The important thing is that these mechanisms should work without any central intervention. These are just two suggestions. Perhaps there are other such mechanisms that we could put in place. Ideas? One thing I have missed ever since I first visited haskell.org is a web forum. I guess most of the people reading/posting on the mailinglists are used to it and like it, but I prefer forums. Actually, I have never posted here before, but I usually read the (for me) intresting parts from the Haskell Archives. However, I have not read a forum-discussion yet, and since noone has proposed it I felt that I should do a post about it. I would tend to disagree. I think the combination of the mailing lists, a wiki and the IRC channel cover most of our communication needs. I don't think that yet another variant would help us much. Web boards tend to be harder to use than email since it requires a web browser. Having too many differnt types of communication channel would reduce the readership of any one of them. Duncan ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
On Fri, Nov 11, 2005 at 03:12:40PM +, Duncan Coutts wrote: I would tend to disagree. I think the combination of the mailing lists, a wiki and the IRC channel cover most of our communication needs. Personally I prefer to use mailing lists, but they have one disadvantage - if you don't set up filters to split incoming mail into multiple folders, you can be flooded with messages. I don't think that yet another variant would help us much. Web boards tend to be harder to use than email since it requires a web browser. Having too many differnt types of communication channel would reduce the readership of any one of them. How about a forum integrated with mailing lists? Best regards Tomasz ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re[2]: [Haskell] Making Haskell more open
Hello Simon, Friday, November 11, 2005, 5:51:55 PM, you wrote: * The GHC user manual [currently generated using DocBook] I think it should continue to be written in DocBook. (It should switch to DocBook XML if it's still using SGML DocBook.) XML documents are type-safe in contrast to LaTeX documents, for example. XML is well supported. DocBook stresses logical markup and allows very specific markup and therefore supports conversion into different formats (HTML, PDF, ...) very well. Again, what do others think? SM We already use DocBook XML, and I'm relatively pleased with it, except SM for the fact that it's far from easy to set up a working DocBook SM toolchain on your system unless your OS of choice is up to date and has SM a well-maintained set of DocBook packages. how it will be possible to contribute in ghc docs? for example, if i wrote template haskell doc in MS Word, can i fo somethong to make it ready to including in ghc docs? -- Best regards, Bulatmailto:[EMAIL PROTECTED] ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Re: Making Haskell more open
On Fri, Nov 11, 2005 at 03:19:27PM +, Duncan Coutts wrote: I cannot imagine that a couple of people is sufficient to review all recent changes and therefore I don't think they do it this way. There are some typical articles where screwing up happens often, so these articles might be regularily revisited. Screwing up of articles might as well be removed by ordinary people who discover ugly things in articles by accident. One possability here would be to have all changes to the wiki reported in real time (or near real time) in the #haskell IRC channel. The #haskell lambdabot could be extended to do this. The #haskell IRC channel is active nearly 24 hours a day and has a membership that varies between 170 and 200. This would easily be enough eyes to spot malicious or inaccurate changes. I think that the amount of changes that need to be reviewed could be dramatically reduced if we create some trust management system, for example we could trust changes made by authorized users. The users who most often contribute to the Wiki will probably be the same who care about reviewing changes and they probably won't mind to log in, so their changes won't have to be reviewed. Best regards Tomasz ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
On Fri, Nov 11, 2005 at 04:52:30PM +0100, Wolfgang Jeltsch wrote: IMO, the best solution are newsgroups. What I dislike with web-based communication (webmail, webforums) is that webbrowsing is not as flexible as using a specialized software and that you are not free in choosing your communication software apart from choosing a webbrowser ??? you have to live with the webmail/webforum software installed on the server, independently of whether you like it or not. That's a good point... or points. I also like newsgroups, but I haven't used them in a while, probably because most of discussions about haskell take place on mailing lists. Maybe it's time to register comp.lang.haskell? Could someone tell me something about fa.haskell? Is it a mirror of [EMAIL PROTECTED] Can it be used to post messages through NNTP? How about a forum integrated with mailing lists? Does such a thing already exist somewhere? Not that I know of. How about an integrated newsgroup+mailinglist+forum. If we had a two-way newsgroup+mailinglist integration, people could use it also as a forum, for example through gmail.google.com. But I don't use fora, so I probably talk nonsense. Best regards Tomasz ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
[Haskell] Making the haskell.org website more open with a wiki? was Re: Making Haskell more open
Wolfgang Jeltsch [EMAIL PROTECTED] writes: Am Freitag, 11. November 2005 12:22 schrieb Udo Stenzel: Seperation of article and discussion is a cultural, not a technical problem. One thing I always disliked about the Haskell Wiki is that you often have a short article and then a lot of user comments. What people searching for information on a certain topic mostly want is a consistent article describing the topic, not a text with a mix of pieces certain users threw in. That's part of the goal of The Monad.Reader, but feel free to refactor Wiki pages from ThreadMode into DocumentMode. (see ThreadMode and DocumentMode on http://c2.com/cgi/wiki?WikiModes ) What HaWiki needs is not yet another wiki engine I think, the discussion was not about basing the HaWiki on a different wiki engine but to create a new wiki which should be a replacement for the whole Haskell website. If a wiki engine in Haskell is a good motivation, there's always Flippi. My only worry with the current wiki is the licensing. There's no overall license required for content contributed, so example code can't be directly used in OSS or commercial projects. I'd like to freeze the wiki at some point and create a new wiki instance with a sensible license, whether it be BSD3, Creative Commons, Gnu FDL, or whatever fits. Moving the existing website to a wiki will solve the problems of community updating, searching, file attachments, and the like. On the other hand, those same problems could also be solved by putting the website into a darcs repository and allowing certain users to push changes. Then anyone could send a patch to one of those certain users. -- Shae Matijs Erisson - http://www.ScannedInAvian.com/ - Sockmonster once said: You could switch out the unicycles for badgers, and the game would be the same. ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
RE: Re[2]: [Haskell] Making Haskell more open
On 11 November 2005 15:48, Bulat Ziganshin wrote: Friday, November 11, 2005, 5:51:55 PM, you wrote: * The GHC user manual [currently generated using DocBook] I think it should continue to be written in DocBook. (It should switch to DocBook XML if it's still using SGML DocBook.) XML documents are type-safe in contrast to LaTeX documents, for example. XML is well supported. DocBook stresses logical markup and allows very specific markup and therefore supports conversion into different formats (HTML, PDF, ...) very well. Again, what do others think? We already use DocBook XML, and I'm relatively pleased with it, except for the fact that it's far from easy to set up a working DocBook toolchain on your system unless your OS of choice is up to date and has a well-maintained set of DocBook packages. how it will be possible to contribute in ghc docs? for example, if i wrote template haskell doc in MS Word, can i fo somethong to make it ready to including in ghc docs? You can either author in DocBook XML directly, or send us chunks of plain text and we'll do the markup for you (obviously we prefer the former, though). Cheers, Simon ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
Am Freitag, 11. November 2005 17:00 schrieben Sie: [...] Maybe it's time to register comp.lang.haskell? You could also setup your own newsserver news.haskell.org and create whatever groups you like there. This way you could create several Haskell groups, corresponding to the mailing lists we have today. The advantage of newsgroups over mailing lists is that newsgroups are designed for discussions among several people and therefore newsgroup software supports this kind of usage very well while mailing lists are actually a hack. [...] Best wishes, Wolfgang ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
Simon Marlow ([EMAIL PROTECTED]) wrote: We already use DocBook XML, and I'm relatively pleased with it, except for the fact that it's far from easy to set up a working DocBook toolchain on your system unless your OS of choice is up to date and has a well-maintained set of DocBook packages. I consider that the structure of the present ghc manual does not need such a rich markup as DocBook which is, imho, not very user-friendly. otoh, I'd prefer something simple (if you want to get contributions from more users) like 'txt2tags' (see e.g. http://txt2tags.sourceforge.net/screenshots.html) which enables one to do lot with very simple markup. There are many targets supported, light sys-reqs, cli gui, and even syntax highlighting for (g)vim, emacs, kate... Sincerely, Gour -- Registered Linux User | #278493 GPG Public Key | 8C44EDCD ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
[Haskell] Re: Making Haskell more open
In article [EMAIL PROTECTED], Udo Stenzel [EMAIL PROTECTED] wrote: MoinMoin supports arbitrarily named links, like so: [anything goes]. But people don't use them. It's the elimination of the other kind that's valuable. If you set the appropriate check mark in your user preferences, RunTogetherWords are displayed as Seperate Word for you. ...which gives Monad Plus instead of MonadPlus. Seperation of article and discussion is a cultural, not a technical problem. Sure, any Wiki can be made to represent the information in any other, just as any Haskell program can be rewritten in Visual Basic. -- Ashley Yakeley, Seattle WA ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
I agree with Gour. I found txt2tags as a result of a discussion on the GTK2HS list. It is simple to use, readable as is, or easily transformable to a variety of targets. Also, it is consistent with bird-track literate Haskell, so I can run my .lhs documents through txt2tags and get html, latex, pretty text, or a bunch of things I haven't tried yet including *.doc (msword) (the latter via txt2tags for html, soffice to go from html to *.doc). John Velman On Fri, Nov 11, 2005 at 06:29:24PM +0100, Gour wrote: Simon Marlow ([EMAIL PROTECTED]) wrote: We already use DocBook XML, and I'm relatively pleased with it, except for the fact that it's far from easy to set up a working DocBook toolchain on your system unless your OS of choice is up to date and has a well-maintained set of DocBook packages. I consider that the structure of the present ghc manual does not need such a rich markup as DocBook which is, imho, not very user-friendly. otoh, I'd prefer something simple (if you want to get contributions from more users) like 'txt2tags' (see e.g. http://txt2tags.sourceforge.net/screenshots.html) which enables one to do lot with very simple markup. There are many targets supported, light sys-reqs, cli gui, and even syntax highlighting for (g)vim, emacs, kate... Sincerely, Gour -- Registered Linux User | #278493 GPG Public Key| 8C44EDCD ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
Tomasz Zielonka [EMAIL PROTECTED] writes: (snip) Maybe it's time to register comp.lang.haskell? (snip) At the least, I find it conspicuous by its absence, given how many other languages I see in comp.lang.* that I think of as less important, and how busy groups like comp.lang.lisp are. In lieu of comp.lang.haskell, comp.lang.functional seems to get most of the Usenet Haskell discussion. Frankly, I'd be happy to see comp.lang.haskell supersede these mailing lists, but I use Gnus for both mail and news so it all looks pretty much the same to me. -- Mark ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
Wolfgang Jeltsch ([EMAIL PROTECTED]) wrote: The advantage of newsgroups over mailing lists is that newsgroups are designed for discussions among several people and therefore newsgroup software supports this kind of usage very well while mailing lists are actually a hack. I do not follow newgroups, but can you please explain a bit what features are in newsgroup software that support this kind of discussion, which are missing in the mailing lists? (Pls. do not see this as a provocation, I'm realy interested to hear.) Sincerely, Gour -- Registered Linux User | #278493 GPG Public Key | 8C44EDCD ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
On Fri, 11 Nov 2005, Gour wrote: Wolfgang Jeltsch ([EMAIL PROTECTED]) wrote: The advantage of newsgroups over mailing lists is that newsgroups are designed for discussions among several people and therefore newsgroup software supports this kind of usage very well while mailing lists are actually a hack. I do not follow newgroups, but can you please explain a bit what features are in newsgroup software that support this kind of discussion, which are missing in the mailing lists? (Pls. do not see this as a provocation, I'm realy interested to hear.) Well, you don't have to be registered to post on it, which is actually rather nice. Also, I think the archiving would work better. The current Haskell mailing list archives don't seem to run very fast. If it was a newsgroup, then you could use google groups to browse through old messages. ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
Creighton Hogg ([EMAIL PROTECTED]) wrote: Well, you don't have to be registered to post on it, which is actually rather nice. Hmmm, iirc, gmane.org wanted me to authorize in order to be able to post though I do not know what is the present policy. Also, I think the archiving would work better. The current Haskell mailing list archives don't seem to run very fast. If it was a newsgroup, then you could use google groups to browse through old messages. I do not experience any delay with the http://www.mail-archive.com/ archive, although it is possible to put e.g. htdig search engine on haskell.org (there are patches for integration with mailman and I put them on few sites.) Besides that, one can always use something like: 'gtk2hs site:www.haskell.org//pipermail/haskell/' as a search term in Google to restrict hits to e.g. 'haskell' mailing list. Sincerely, Gour -- Registered Linux User | #278493 GPG Public Key | 8C44EDCD ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
[Haskell] CfP LDTA 2006
Call for Papers
for
Sixth Workshop on
Language Descriptions, Tools and Applications
LDTA 2006
A satellite event of ETAPS 2006
in Cooperation with ACM SIGPLAN
Saturday, April 1, 2006 in Vienna, Austria
http://ldta06.cs.umn.edu
Scope:
--
The aim of this one-day workshop is to bring together researchers from
academia and industry interested in the field of formal language
definitions and language technologies, with a special emphasis on
tools developed for or with these language definitions. This active
area of research involves the following basic technologies:
- Program analysis, transformation, and generation
- Formal analysis of language properties
- Automatic generation of language processing tools
For example, language definitions can be augmented in a manner so that
not only compilers or interpreters can be automatically generated but
also other tools such as syntax-directed editors, debuggers, partial
evaluators, test generators, documentation generators, etc. Although
various specification formalisms like attribute grammars, action
semantics, operational semantics, and algebraic approaches have been
developed, they are not widely exploited in current practice.
It is the aim of the LDTA workshops to bridge this gap between theory
and practice. Among others, the following application domains can
benefit from advanced language technologies:
- Software component models and modeling languages
- Re-engineering and re-factoring
- Aspect-oriented programming
- Domain-specific languages
- XML processing
- Visualization and graph transformation
- Programming environments such as Eclipse, .net, Rotor, SUN Java, etc.
The workshop welcomes contributions on all aspects of formal language
definitions, with special emphasis on applications and tools developed
for or with these language definitions.
Invited Speaker:
The invited speaker for LDTA 2006 is Jean Bezivin, Universite de
Nantes.
Important Dates:
- Submission deadline: December 1, 2005.
- Notification: January 16, 2006
- Final version due: February 15, 2006
- Workshop: April 1, 2006
Submission Procedure and Publication:
-
Submission will be open from autumn 2005. Two classes of papers are
solicited: full-length research papers and short tool-demo papers.
Tool-demo papers should contain a brief description of the tool and
include a section that clearly explains what will be demonstrated.
Full-length papers should be at most 15 pages in length and tool-demo
papers should be at most 4 pages in length. Both classes of papers
should be submitted electronically as PostScript or PDF files to both
of the program committee chairs, John Tang Boyland at
[EMAIL PROTECTED] and Tony Sloane at [EMAIL PROTECTED] The
message should also contain a text-only abstract and contact author
information.
Additional submission details, along with LaTeX style files, are
available on the LDTA 2006 web page: \texttt{ldta06.cs.umn.edu}. The
final versions of accepted papers will be published in Electronic
Notes in Theoretical Computer Science (ENTCS), Elsevier Science, and
will be made available during the workshop.
The authors of the best full-length papers will be invited to write a
journal version of their paper which will be separately reviewed and,
assuming acceptance, be published in journal form. As in past years,
this will be done in a a special issue devoted to LDTA 2006 of the
journal Science of Computer Programming (Elsevier Science).
Program Committee:
--
- Uwe Assmann, Dresden Technical University, Germany
- John Tang Boyland, University of Wisconsin-Milwaukee, USA
(co-chair), [EMAIL PROTECTED]
- Jim Cordy, Queen's University, Canada
- Jan Heering, Centrum voor Wiskunde en Informatica (CWI), The
Netherlands
- Nigel Horspool, University of Victoria, Canada
- Johan Jeuring, Utrecht University, The Netherlands
- Adrian Johnstone, Royal Holloway, University of London, UK
- Steven Klusener, Vrije Universiteit, The Netherlands
- David Lacey, University of Warwick, United Kingdom
- Brian Malloy, Clemson University, USA
- Paul Roe, Queensland University of Technology, Australia
- Michael Schwartzbach, BRICS, University of Aarhus, Denmark
- Tony Sloane, Macquarie University, Australia (co-chair),
[EMAIL PROTECTED]
- Yannis Smaragdakis, Georgia Institute of Technology, USA
- David Watt, University of Glasgow, Scotland
- David Wile, Teknowledge Corp, USA
Organizing Committee:
-
- Eric Van Wyk, University of Minnesota, Minneapolis, USA,
[EMAIL PROTECTED]
- Joost Visser, University of Minho, Braga, Portugal,
[EMAIL PROTECTED]
___
Haskell mailing list
Re: [Haskell] Making Haskell more open
On Fri, Nov 11, 2005 at 05:00:52PM +0100, Tomasz Zielonka wrote: How about an integrated newsgroup+mailinglist+forum. If we had a two-way newsgroup+mailinglist integration, people could use it also as a forum, for example through gmail.google.com. Of course I meant groups.google.com Best regards Tomasz ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
Tomasz Zielonka [EMAIL PROTECTED] writes: (snip) How about an integrated newsgroup+mailinglist+forum. If we had a two-way newsgroup+mailinglist integration, people could use it also as a forum, for example through gmail.google.com. But I don't use fora, so I probably talk nonsense. That would be nice if the References: and In-Reply-To: headers could still be properly managed so that contributions from one side wouldn't break threading in another. -- Mark ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] [ANNOUNCE] yhc - York Haskell Compiler
On 11/11/05, Neil Mitchell [EMAIL PROTECTED] wrote: Just so that people don't get the wrong idea ... - It's just an experiment of mine with the backend that turns out to have sparked some interest. It seems to compile most of Haskell 98 (at least it did when it last worked ;-)) but it's in no way an industrial strength compiler yet. I'm curious. Can you be more specific about what you thought wanted/needed changing in nhc98's VM and/or compiler? I haven't played around with nhc98 yet, but I was intrigued by its small size and its (modestly-sized and simple) bytecoded implementation. Should I now be more interested in Yhc instead? ;-) I'd like to build a web-publishing framework in Haskell that is totally self-contained, very portable, and easy to bootstrap ... and nhc98 or Yhc might be a nice place to start. Are you documenting your thoughts about the Yhc implementation somewhere? Cheers, - David -- There's more than one way to do it: the Perl way, and the _right_ way. ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] [ANNOUNCE] yhc - York Haskell Compiler
On 11 Nov 2005, at 23:09, David Frech wrote: On 11/11/05, Neil Mitchell [EMAIL PROTECTED] wrote: Just so that people don't get the wrong idea ... - It's just an experiment of mine with the backend that turns out to have sparked some interest. It seems to compile most of Haskell 98 (at least it did when it last worked ;-)) but it's in no way an industrial strength compiler yet. I'm curious. Can you be more specific about what you thought wanted/needed changing in nhc98's VM and/or compiler? I haven't played around with nhc98 yet, but I was intrigued by its small size and its (modestly-sized and simple) bytecoded implementation. Should I now be more interested in Yhc instead? ;-) I'd like to build a web-publishing framework in Haskell that is totally self-contained, very portable, and easy to bootstrap ... and nhc98 or Yhc might be a nice place to start. Are you documenting your thoughts about the Yhc implementation somewhere? You should find us documenting our work in the blog... yhc06.blogspot.org. Bob ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] [ANNOUNCE] yhc - York Haskell Compiler
Sorry, I could have done with answering a bit more there... On 11 Nov 2005, at 23:09, David Frech wrote: I'm curious. Can you be more specific about what you thought wanted/needed changing in nhc98's VM and/or compiler? Basically, nhc98's backend had several problems, most notably not being portable to windows, and the high memory bug (which I have on reliable sources would have been pretty nasty to fix). I can't really say anything more about Tom's reasons for rewriting it, because I don't know how much he wants to be public. Suffice to say, there are more benefits to the rewrite :). I haven't played around with nhc98 yet, but I was intrigued by its small size and its (modestly-sized and simple) bytecoded implementation. Should I now be more interested in Yhc instead? ;-) As far as the YHC team is concerned, yes... As far as the nhc team is... I'm not sure, perhaps Malcolm or Colin would be kind enough to tell us. I'd like to build a web-publishing framework in Haskell that is totally self-contained, very portable, and easy to bootstrap ... and nhc98 or Yhc might be a nice place to start. Yhc is certainly a good place to start - it's extremely easy to bootstrap on many many platforms. Thanks Bob ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
On Friday 11 November 2005 13:56, Wolfgang Jeltsch wrote: Am Donnerstag, 10. November 2005 12:27 schrieb Simon Peyton-Jones: [...] * The GHC user manual [currently generated using DocBook] I think it should continue to be written in DocBook. (It should switch to DocBook XML if it's still using SGML DocBook.) XML documents are type-safe in contrast to LaTeX documents, for example. XML is well supported. DocBook stresses logical markup and allows very specific markup and therefore supports conversion into different formats (HTML, PDF, ...) very well. Again, what do others think? Yes. In fact I like the current GHC manual as it is. How would we make sure it stayed organised? And avoid getting screwed up by malicious folk? At Wikipedia, you can log in and modify content and you can modify content while not being logged in. In the first case, the history mentions your username, in the second case, it mentions your IP address. I think, MediaWiki can be configured so that only logged-in users are able to do modifications. As far as I can remember, I once saw a site using MediaWiki, which didn't allow modifications from non-registered users. But honestly, would we need to protect ourselfs from malicious folk? At Wikipedia, they have problem with malicious people at a couple of articles, so they sometimes have to lock articles. (This tells us that article locking obviously is another feature of WikiMedia. As far as I know, this kind of locking can be done by different persons, not just one super user.) But who would want to screw up pages about Haskell? Spambots are the worst problem, I guess. Ben ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Making Haskell more open
On Saturday 12 November 2005 02:30, Benjamin Franksen wrote: On Friday 11 November 2005 13:56, Wolfgang Jeltsch wrote: Am Donnerstag, 10. November 2005 12:27 schrieb Simon Peyton-Jones: [...] * The GHC user manual [currently generated using DocBook] I think it should continue to be written in DocBook. (It should switch to DocBook XML if it's still using SGML DocBook.) XML documents are type-safe in contrast to LaTeX documents, for example. XML is well supported. DocBook stresses logical markup and allows very specific markup and therefore supports conversion into different formats (HTML, PDF, ...) very well. Again, what do others think? Yes. In fact I like the current GHC manual as it is. Sorry, that comment seems to miss the point. What I wanted to say is: However the source format is going to be changed to better support user contributions, I would like it to remain similar in its (processed) end user appearance. Ben ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
[Haskell] Re: Making Haskell more open
In article [EMAIL PROTECTED], Till Mossakowski [EMAIL PROTECTED] wrote: I have also made nice experiences with MediaWiki/WikiPedia. However, I think while you can include images on MediaWiki pages, you cannot include documents (like ps or pdf) - these have to be external links. Of course, the possibility of including such documents would be a desirable feature for a system of Haskell documentation pages. Perhaps it is not too difficult to add this feature for a MediaWiki expert? In the current shipping version, 1.5.2, you can allow uploads of PDF, etc. by adding this to your LocalSettings.php: $wgCheckFileExtensions = false; $wgStrictFileExtensions = false; Even with these settings, dangerous content such as .php, .js and .html files is prevented. Uploaded PDFs work fine, and display inline as the PDF logo. -- Ashley Yakeley, Seattle WA ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
[ ghc-Bugs-1353390 ] unknown exception
Bugs item #1353390, was opened at 2005-11-10 19:20 Message generated for change (Settings changed) made by simonmar You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=108032aid=1353390group_id=8032 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Compiler Group: 6.4.1 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Rich (rmfought) Assigned to: Nobody/Anonymous (nobody) Summary: unknown exception Initial Comment: Compiling hsgnutls-0.2.1, get the following error: Glasgow Haskell Compiler, Version 6.4.1, for Haskell 98, compiled by GHC version 6.4 Using package config file: /usr/lib/ghc-6.4.1/package.conf Hsc static flags: -static *** Chasing dependencies: Chasing modules from: Setup.lhs *** Literate pre-processor /usr/lib/ghc-6.4.1/unlit -h Setup.lhs Setup.lhs /tmp/ghc15830.lpp Stable modules: *** Compiling Main ( Setup.lhs, Setup.o ): compile: input file /tmp/ghc15830.lpp *** Checking old interface for Main: Skipping Main ( Setup.lhs, Setup.o ) *** Deleting temp files Deleting: /tmp/ghc15830.s Warning: deleting non-existent /tmp/ghc15830.s Upsweep completely successful. *** Deleting temp files Deleting: link: linkables are ... LinkableM (Thu Nov 10 09:33:46 CST 2005) Main [DotO Setup.o] Linking ... *** Deleting temp files Deleting: /tmp/ghc15830.lpp ghc-6.4.1: ghc-6.4.1: panic! (the `impossible' happened, GHC version 6.4.1): unknown exception This occured after I unregistered Cabal-1.0 , and installed Cabal 1.1.1. The compilation went fine before this. -- Comment By: Simon Marlow (simonmar) Date: 2005-11-11 11:06 Message: Logged In: YES user_id=48280 The error message is at fault - it is trying to compain about a missing package. You probalby have another package that depends on the Cabal-1.0 that you removed. The bug has been fixed, the fix will be in 6.4.2. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=108032aid=1353390group_id=8032 ___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
RE: class aliases
John | If I were to implement my class alias proposal for ghc in an acceptably | clean way, would it be accepted? There appeared to be enough interest to | support at least experimentation with it and I would have no issues with | it being dropped in the future if it turned out to not be useful. Yes, definitely; that would be great. I would like to interact with you as you did it, rather than be presented with a completed result, because I'm sure I'll have lots of ideas about what a clean implementation would look like. I'd also like to take another look at the design (which you may have refined a bit since your initial message). So let me know when you feel like taking up the cudgels and we can discuss it in a bit more detail. Simon ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
[Haskell-cafe] throwDyn typing fun
Hello It seems that the type of throwDyn and throwDynTo are dangerously close. ThrowDyn works in with any of the arguments of throwDynTo, which can cause evil situations. throwDyn :: Typeable exception = exception - b Which means e.g. throwDyn someThreadId SomeException will work when you wanted to say throwDynTo someThreadId SomeException and they both have types which unify with IO (). I think using a class Typeable = DynamicException a where ... and throwDyn :: DynamicException a = a - b could make more sense. - Einar Karttunen ___ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
Re: [Haskell-cafe] throwDyn typing fun
On Fri, Nov 11, 2005 at 01:20:05PM +0200, Einar Karttunen wrote: It seems that the type of throwDyn and throwDynTo are dangerously close. ThrowDyn works in with any of the arguments of throwDynTo, which can cause evil situations. throwDyn :: Typeable exception = exception - b Which means e.g. throwDyn someThreadId SomeException will work when you wanted to say throwDynTo someThreadId SomeException and they both have types which unify with IO (). How evil! ;-) I think using a class Typeable = DynamicException a where ... and throwDyn :: DynamicException a = a - b could make more sense. You could also do something like: newtype Exn a = Exn a -- not Typeable throwDyn' :: Typeable exception = Exn exception - b throwDyn' (Exn e) = throwDyn e used as throwDyn' (Exn (some-typeably-thingy)) then neither (throwDyn' someThreadId SomeException) nor (throwDyn' someThreadId (Exn SomeException)) will compile. And you won't have to create instances of DynamicException, but it is probably more ugly. Best regards Tomasz ___ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
[Haskell-cafe] How to use a wiki to annotate GHC Docs? was Re: [Haskell] Re: Making Haskell more open
Malcolm Wallace [EMAIL PROTECTED] writes: ... And avoid getting screwed up by malicious folk? ... but I believe there are a number of people who regularly review all the Recent Changes and undertake to 'undo' any malicious/inaccurate modifications. I suspect this would end up adding /more/ work to central maintainers, rather than less. Recently the Haskell Wiki went from anonymous edits to logged-in edits because of the tremendous amount of wikispam, so I agree with this. On the good side, it's easy to create an account. On the bad side, at some point spambots will notice this too. Fermat's Last Margin was originally planned to annotate images attached to wiki pages. Someone on #haskell suggested using SVG instead, and someone else showed me that pstoedit can produce SVG from pdf and ps files. So, generalized markup annotation might be a good approach. Since Fermat's Last Margin is just a darcs-backed wiki, that might be simpler. If the ghc-docs were viewable and editable in a wiki format, and the changes were saved to a darcs repo, then the maintainers could just pull the changes they like, and flush useless changes like spam. -- Shae Matijs Erisson - http://www.ScannedInAvian.com/ - Sockmonster once said: You could switch out the unicycles for badgers, and the game would be the same. ___ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
[Haskell-cafe] Re: Making Haskell more open
On Fri, 11 Nov 2005, Tomasz Zielonka [EMAIL PROTECTED] wrote: [Moved to cafe.] How about an integrated newsgroup+mailinglist+forum. If we had a two-way newsgroup+mailinglist integration, people could use it also as a forum, for example through gmail.google.com. But I don't use fora, so I probably talk nonsense. I think Gmane has everything you're looking for (bidirectional mail-to-news gateway, you can read and post via a web page, and quite a few Haskell mailing lists are already archived there; see http://dir.gmane.org/gmane.comp.lang.haskell.general, for instance). I've hardly used it, though, so I can't tell whether it works well. -- /NAD ___ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
[Haskell-cafe] `typeof' is not a (visible) method of class `Typeable' ?
Hi All, While I was trying to declare Language.Haskell.TH.Exp as an instance of Typeable, ghci 6.4 yields this error. It does not allow me to define an instance of typeof. Does anybody know what should be the right way of doing this? Thanks. -W-M- @ @ | \_/ ___ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
Re: [Haskell-cafe] `typeof' is not a (visible) method of class `Typeable' ?
On Friday 11 November 2005 18:22, WANG Meng wrote: Hi All, While I was trying to declare Language.Haskell.TH.Exp as an instance of Typeable, ghci 6.4 yields this error. It does not allow me to define an instance of typeof. Does anybody know what should be the right way of doing this? Thanks. Did you try 'typeOf' (note the capital O)? Ben ___ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
