- Timber - Haskell.org

exciting!
by Raoul Duke 29 Sep '09

29 Sep '09

ok, i won't have time to really dig in to Timber, but i'm excited to see it progressing. congratulations and thanks for your hard work. sincerely.

1 0

64 bit?
by Rick R 04 Jun '09

04 Jun '09

I haven't looked too deeply into the source, but it would appear that the bulk of the 64-bit problems are relegated to rts.h. Is there any effort under way to address this? If not, I will take a whack at correcting it. If there is some experimental code out there, I'd be happy to test it on my 64 bit fedora machine. -- We can't solve problems by using the same kind of thinking we used when we created them. - A. Einstein

2 9

building from trunk
by Rick R 21 May '09

21 May '09

I grabbed the latest from darcs, and upon attempting to run runhaskell Setup.lhs configure I got the response: Setup.lhs: At least the following dependencies are missing: binary >=0.4.2, bzlib >=0.4.0.0 But I have those particular libraries installed in cabal. Am I missing an additional parameter? Thanks, Rick -- We can't solve problems by using the same kind of thinking we used when we created them. - A. Einstein

3 3

ANNOUNCE: The Timber compiler 1.0.3
by Johan Nordlander 19 May '09

19 May '09

----------------------------------- ANNOUNCE: The Timber compiler 1.0.3 ----------------------------------- We're pleased to announce the availability of version 1.0.3 of the Timber compiler. Timber is a modern language for building event-driven systems, based around the notion of reactive objects. It is also a purely functional language derived from Haskell, although with a strict evaluation semantics. The Timber compiler currently runs on Linux and MacOS X platforms, but uses gcc as its back-end so it should be easily portable to most POSIX-like environments. This is a bug fix release that is intended to pave the way for a more substantial version currently under development. Version 1.0.3 can be summarized as "improved overall stability, with very minor added features". For more info, detailed release notes, language documentation, source code access and binary installers, see http://timber-lang.org/ Or simply grab the timberc package at http://hackage.haskell.org/. *** A dedicated Timber mailing list hosted at haskell.org is now also available. *** See link at http://timber-lang.org/ for subscription info. The Timber Team through Johan Nordlander

1 0

Compiler milestone
by Johan Nordlander 23 Feb '07

23 Feb '07

Friends, I'm happy to report that the Timber compiler is now in a such a state that I believe it's time to switch focus to testing. All passes are implemented and no crucial functionality is left out. However, very few test runs have been done up to this point, which means that we are still far from having a running compiler. The run- time system also haven't been checked in yet, but it will be in a day or two. Still I'd be happy for some help producing dry-run test examples at this stage, before we risk getting stuck with issues that relate to I/O and Unix interfacing. My suggestion is that we split the testing activities into two phases: 1. Random testing of everyone's favorite code snippets. First goal is to produce C output only, then in a few days also to make them run. This is likely to draw attention to many of the (no doubt) numerous simple and silly bugs that hinder normal operation. While this activity might generate a lot of error reports initially it should hopefully also lead to a relatively well-behaved compiler in a rather short time. I expect to do most of the bug-hunting myself while in this phase. 2. Systematic testing of all branches of every individual pass. This should probably be combined with careful documentation, perhaps also with writing/revising the language definition. To make this work feasible we should split it up in some sensible way, although it's probably wise to wait until phase 1 is over until we make an attempt at organizing phase 2. I also have a list of minor areas of the compiler that still need to be completed, as well as some discussion points regarding the actual language design. But again it's probably best to defer these issues until we at least have a compiler that runs the basic test examples. So if you're interested in the long term goal and prepared for some initial disappointments, pull out the latest darcs version and generate some error reports! Send them directly to me and I'll respond to the list after each update to the sources. Happy lumbering! Johan

3 4

Re: Failing configure in Timber
by Andy Gill 09 Jan '07

09 Jan '07

On Jan 4, 2007, at 2:45 PM, Johan Nordlander wrote: > Hi Andy, and Happy New Year! Happy New Year! > > I'm having problems accessing darcs.haskell.org, otherwise you > would have seen some recent pushes from my side. Do you know the > status of that machine and when we should expect to see it up and > running again? > It seems to be working fine now. Can you email me as soon as you see any problem, because explicitly galois maintain this machine, specifically to help the GHC crowd. > Speaking of administration, I believe it would be a good idea to > relay all darcs push messages to the timber list (we can probably > do without a specific commit list at this stage). Is this easy to > fix from your side? I'll look into this. Does anyone know how to do this? > >> Thanks! I'll look forward to more coming down the pipe. >> >> Is there something you would like me to look at/add? I planning on >> adding some >> parser tests as a start, but there might be something better to do. > > All kinds of tests would be valuable, we need to establish a test > suite rather quickly. Building a test suite for the parser is > probably also a good opportunity to get acquainted with the finer > details of the language ("what on earth is this construct supposed > to mean?"). Moreover, there is much room for improving the > grammar, e.g. for the purpose of avoiding the shift/reduce > conflicts we currently have (or at least understanding them > better). So you're very welcome to work on that part. However, my > pending patches contain some changes to the parser, so you might > want to wait for my update. > I built a trivial test framework, and I'll check to see if it is checked in to the timber darcs. It should be easy to use to test the parser. I'm also working on a coverage tool for Happy (via the Hpc work), so we can check that we've actually use every production in our grammar in our tests. > Another good place to look at would be the Kindle2C pass, once I'm > able to commit the Core2Kindle conversion (at least that might make > the connection between KIndle and Timber clearer). It's not very > far away now, but doing it properly has required some changes to > the way the "self" variable is handled by the front end (and has > even suggested some uninteresting changes to the language > itself...!). I'll still need a couple of days to finish it off. > > Then we must update the lambdalifter to the changes made to Kindle, > but once that's done we should essentially have a running > compiler! However, very little testing has been done, so we'll > probably have to spend quite some time hunting bugs and building up > a test suite. My intention is to ease that process by adding > extensive comments to all modules, along the lines of my recent > changes to Syntax2Core. > > BTW, I suggest we move all these discussions to the timber list > from now on. Some of our recent conversations might also be of > interest to the others, so perhaps we should forward a few messages > to the list if it's ok with you. > Sure. I'm happy to have any of these discussions on the timber list. (I've forward this email to timber(a)haskell.org. I'm looking forward to the working compiler. As we add tests, we should be able to make progress quickly. There are also rumblings of an Ajax based Haskell debugger that could be used by Timber without to much extra effort; the main issue is getting accurate span locations into the Timber-level AST. AndyG

2 3

Welcome to the timber list
by Andy Gill 14 Dec '06

14 Dec '06

Guys! Welcome to the Timber list. lots to do. One thing I'd like to visit is String = [Char]. Is this the right thing for Timber? We have data [a] = ... , how about data Vector a = ... where Vector is an 0 index'd array, and, String = Vector Char? Is this too much of a departure from Haskell? What parts of Haskell type classes might we want to keep? Can we simplify the hierarchy? Both of these questions relate to how much of Haskell we carry forward, and how much we change. AndyG

2 2

Test of timber email
by Andy Gill 05 Dec '06

05 Dec '06

Test of timber email

1 0