- Haskell - Haskell.org

Re: [Haskell] Making a spreadsheet with Haskell
by S.J.Thompson 14 Feb '04

14 Feb '04

You could take a look at Vital http://www.cs.kent.ac.uk/projects/vital/ >From the web page: Vital is a visual programming environment based on Haskell, a contemporary functional programming language. It is particularly intended for supporting the open-ended, incremental style of development often preferred by end users (engineers, scientists, analysts, etc.). It may also be useful for teaching Haskell. Simon

1 0

GHC Core & backend
by Arjan van IJzendoorn 14 Feb '04

14 Feb '04

Hello all, Is anybody using GHC's backend as a backend for their own compiler? In the paper "An external representation for the GHC Core Language" the introduction states that "there are many (undocumented) idiosyncracies in the way GHC produces Core from source Haskell". And that "it will be hard to produced Core that can be integrated with GHC-produced core, and we don't aim to support this". Has this changed since the time of writing this paper? It would be cool if, let's say, Helium (http://www.cs.uu.nl/helium) could use all of GHC's libraries... Regards, Arjan van IJzendoorn

2 1

Making a spreadsheet with Haskell
by Miren Cob Isasi de Virgala 13 Feb '04

13 Feb '04

> Hi, I would like to know how can I make a spreadsheet using Haskell > (something like Excel, a very-reduced version, of course) > Do I need any kind of special library? How can I make the interface so the > user can introduce data, select data and so on? > > Thanks for your help. > Miren Cob Isasi de Vírgala >

3 2

Website redesign
by John Peterson 13 Feb '04

13 Feb '04

So there it was - another email message complaining about something on haskell.org. "Your site is so `last century'". So I, as usual, said "If you want it fixed, do it yourself". And thus the new look on haskell.org. Thanks much to Jon Lingard for giving us a facelift. The new look (same old content) is very professional. John

1 0

RE: [Haskell] GHC 64bit?
by Simon Marlow 13 Feb '04

13 Feb '04

> Dell's poweredge server with the max 12gb RAM costs $15k. > Moore's law says that > 1. you only need an extra bit/year. > 2. processing that extra bit will cost 50% less next year > > Though perhaps processing time is not linear with > the number of bits for historical/architectural > reasons....? > > I presume that, if we are conservative in the > number of bits we use then we don't run into the > ptr driven storage problem that Axel described. > > In particular, if we need only 2 or 4 times as > much memory, we should only grow pointers by 1 or > 2 bits...rather than growing immediately all the > way to 64... > > Perhaps there could be a command line option to > specify desired ptr size. I assume it is > impossible to adjust pointer size dynamically at > runtime depending on memory consumption (I > assume you would do it at garbage collection time > if it were possible). Using pointers of a size other than the machine's native word size should be possible. We experimented recently with adding tag bits to pointers, and in the process discovered all the places where you would need to convert between "abstract" pointers and real pointers, which are the same places you would need to modify if you were to use some kind of compressed representation for pointers. Cheers, Simon

1 0

RE: [Haskell] GHC 64bit?
by Simon Marlow 13 Feb '04

13 Feb '04

> alex: > > Is there a maximum memory GHC can use/reach? > > Specifically, can GHC address more than 4gb of > > memory? > > SimonM may want to comment, but at the moment I think GHC is > limited to > 4G, but only due to lack of 64bit machines/demand on the developers. > > If you look in ghc/rts/MBlock.h you'll see some references to this. > > I *think* it would be easy to overcome this limit. > > (this should really be on glasgow-haskell-users) In principle, there's no problem. In practice, GHC's storage manager needs a (fast) function of type Ptr a -> Bool to indicate whether a particular address is part of the dynamic heap or not. This is currently implemented as a bytemap, which is 4k long on a 32-bit machine. To cover the whole of a 64-bit address space, this method isn't practical. Nevertheless, we can extend the bytemap to cover a lot more real memory, as long as we have a way to map from virtual memory addresses to elements of the bytemap - this is the tricky bit. So far we haven't tackled this problem in a general way. Cheers, Simon

2 1

Ann: Halipeto 1.1 (web page templates)
by andrew cooke 13 Feb '04

13 Feb '04

Hi, Halipeto generates web pages from templates (much like JSP, Zope TAL etc). It's written in Haskell (with a ghc extension) and is available from http://www.acooke.org/jara/halipeto An example site generated using Halipeto, containing some Pancito images, is at http://www.acooke.org/pancito - the code for that site is included in the Halipeto download as an example. Some details: - The design makes it easy to call Haskell functions from the XHTML template files. - Only static pages are generated. There is no integration with a web server (maybe someone would like to do this? ;o) - XML code is from HaXml (thanks very much!). - Currently a simple text (file/directory) database is used, but care has been taken (the IO monad is threaded through the code) to allow intergration of an SQL backend. Cheers, Andrew -- personal web site: http://www.acooke.org/andrew personal mail list: http://www.acooke.org/andrew/compute.html

1 1

Call for Workshop Proposal:GPCE'04 -- Generative ProgrammingandComponent Engineering
by Simon Marlow 13 Feb '04

13 Feb '04

[ posted on behalf of Benaissa, Zino <zino.benaissa(a)intel.com> ] CALL FOR WORKSHOP PROPOSALS --------------------------------------------------------------------- Third International Conference on Generative Programming and Component Engineering (GPCE'04) Vancouver, October 24-28, 2004 co-located with <http://oopsla.acm.org/> OOPSLA 2004 and <http://www.research.ibm.com/ismm04/> ISMM 2004 <http://gpce04.gpce.org/> http://gpce04.gpce.org ------------------------------------------------------------------------ ----------------------------- Important Dates Submission date: March 19, 2004 Overview Important Dates GPCE workshops provide intensive collaborative environments where generative and component technologists meet to surface, discuss, and solve challenging problems facing the field. Workshops occur on the day before the conference. To ensure a sufficiently small group for effective interaction, workshop organizers manage attendance based on an objective criterion, typically, a short position paper submitted by potential attendees. Other criteria are permitted as long as they are clearly specified in the workshop's call for participation. We encourage proposals for innovative, well-focused workshops on a broad spectrum of component engineering and generative programming topics. All topics related to generative programming and component engineering are potential candidates for workshops. Workshops typically fall into the following categories: * A workshop may address a specific sub-area of generative and component technology in depth. * A workshop may cover areas that cross the borders of several sub areas. Workshops that cross the borders of the formal and the applied areas is one example. * A workshop may focus on the applications and deployment of generative and/or component technology in areas such as telecommunications, mobile computing or real-time systems. Workshops reporting on industrial experiences are particularly welcome. Workshop topics are by no means limited to the types mentioned above. However, in each case, the proposed area is supposed to have enough impetus to yield new results that can be considered important and worth more detailed investigation. What should a proposal look like? Workshop proposals should be sent in ASCII or PDF format to the workshop chair, and they should consist of four pages/parts: 1. Cover Page * Name of the proposed workshop. * Names and addresses of the organizers. * Intended number of participants. * Requested Audio/Video equipment. 2. Abstract * Why it is relevant to GPCE and a short overview of the rationale for the workshop and the major topics. In particular, statements about the review process and ways to ensure creativity during the workshop would be appreciated. * The abstract should preferably not exceed 200 words. 3. Call for Participation * A preliminary version of the Call for Participation that the organizers must prepare if the workshop is accepted. * Should provide a brief overview of the proposed workshop including a description of the goals of the workshops and the work practices. * May repeat some of the statements made on the abstract page, but should be targeted specifically to potential workshop participants. 4. Organizers * Short biography of each organizer. * References to similar workshops organized at previous conferences, including the number of participants. * If a workshop is accepted, the organizers will be requested to prepare a WWW page that will contain the latest information about the workshop. The web pages of each workshop will be linked to the GPCE workshop web site. * Each workshop must have at least two organizers, preferably from different organizations. Preference will be shown to workshops that have more organizers. Workshop organizers and participants have to register for the conference. Recommendations * Workshop organizers should in particular take care to foster the creative potential that is tentatively present in a workshop. * Remember that a workshop is NOT a conference! * The success of a workshop depends greatly on the results generated on-site. * A number of interrelated issues should be taken into account in order to provide a good framework for such on-site creativity. * Time allocation * During the workshop, enough time should be reserved for collaborative work. * Such creative sessions should have a precise topic and objective and their results should be written down so that they can be reported later. Reasonable expectations * One should not count on people's instantaneous and proactive participation. * For many reasons, participants tend to prefer a consumer role much to a producer role during a workshop. * Thus prescreened presentations, even formally reviewed papers, should usually precede any creative sessions. Task forces * Large groups tend to behave like an audience, whereas groups of four to eight people are much more likely to interact. * When planning collaborative sessions, consider having several smaller groups rather than one large group in order to foster the generation of new ideas. * Presentation selection * Quality should obviously be the primary criterion for selecting the presentations. * However, in order for a workshop to be productive, consider also having presentations on some new, controversial topics to spark discussion. * Participant selection * Although the number of workshop participants does not need to be restricted to the selected presenters, the overall size of the workshop should remain small enough to foster creativity. * Usually this means less than 20 participants. Submission Process Electronic submission of proposals is required--send to <mailto:workshops04@gpce.org> workshops04(a)gpce.org. Proposals must be submitted no later than March 19, 2004, BUT EARLIER IS BETTER, as it allows for a more satisfactory coordination between workshop proposals. Proposal Review and Acceptance The proposals received will be reviewed by the Workshop Committee to determine a high quality and appropriate mix for the conference . Important Dates Workshop proposals schedule * Submission deadline for workshop proposals: March 19, 2004 * Notification of workshop acceptance: April 5, 2004 * Workshop program posted on the website: August 31, 2004 This call for participation is for workshop organizers; a later call will occur for workshop attendees. Workshop attendee schedule (all workshops): * Calls for Workshop Paper Submissions issued: April 15, 2004 * Workshop paper submission deadline: July 1, 2004 * Workshop papers - notification of acceptance: August 31, 2004 * Workshop papers - final versions posted at the workshop sites: October 20, 2004 * Workshop day: Monday, October 25, 2004 Workshop chair zino benaissa (Intel Corporation) For More Information For additional information, clarification, or questions please feel free to contact the Workshop Chair.

1 0

GHC 64bit?
by S. Alexander Jacobson 13 Feb '04

13 Feb '04

Is there a maximum memory GHC can use/reach? Specifically, can GHC address more than 4gb of memory? -Alex- _________________________________________________________________ S. Alexander Jacobson mailto:me@alexjacobson.com tel:917-770-6565 http://alexjacobson.com

5 6

Change of editors for HC&A Report
by C.Reinke 12 Feb '04

12 Feb '04

I am happy to report that the half-yearly editions of the ----------------------------------------- Haskell Communities and Activities Report (next edition: May 2004) http://www.haskell.org/communities/ ----------------------------------------- are going to continue as planned, thanks to Arthur van Leeuwen, Universiteit Utrecht, who has kindly agreed to take on the May 2004 edition, and Andres Loeh, also at Utrecht, who has offered to take over as editor starting from November 2004. For those of you who haven't heard of these reports before, have a look at the web site - you should find them interesting reading. They come out twice a year (May/November, since November 2001), with the goal of helping to improve the communication between the increasingly diverse groups, projects, and individuals working on, with or inspired by Haskell. The idea of these reports is simple: Every six months, a call goes out to all of you on the Haskell mailing list to contribute brief summaries of your own area of work. Many of you respond (eagerly, unprompted, and well in time for the deadline;-) to the call. The editor then collects all these into a single report and feeds it back to this very mailing list. A big thanks to Arthur and Andres for volunteering to keep these reports alive, and I hope that everyone else will support their work at least as well as you have supported mine (just continue to do good work, and be ready to talk about it). It has certainly been an interesting time, and I look forward to reading my first HC&A report from the other side!-) So please make sure to reserve some time in April for writing a brief summary of your favourite Haskell activities (Arthur will send his call for contributions in the not too distant future). Happy Haskelling, Claus -- Computing Laboratory University of Kent http://www.cs.kent.ac.uk/~cr3/

1 0