Simon was talking about loading an all.T file as a Haskell file, i.e.
going the EDSL route, I think.
Exactly. Replicating the testsuite as it currently is -- an EDSL -- in
Haskell, would be hard and the results would be unsatisfactory I think. As
you say, if you switch to data rather than co
Claus Reinke wrote:
or, how about a separate repo for all the parts of the developer
wiki relevant to building, testing, hacking, and a cron job that
records and pushes from the wiki files nightly?
Ideally Trac would use darcs as its backend, and I could run a local
Trac against a local darcs
Ian Lynagh wrote:
On Wed, Sep 12, 2007 at 08:43:51PM +0100, Claus Reinke wrote:
"use the source"?-) test descriptions sound like data+read, with a
test driver to be compiled once when the format changes, not when
the description changes.
Right, if you don't go for an EDSL then interpreted lang
On Wed, Sep 12, 2007 at 08:43:51PM +0100, Claus Reinke wrote:
>
> "use the source"?-) test descriptions sound like data+read, with a
> test driver to be compiled once when the format changes, not when
> the description changes.
Right, if you don't go for an EDSL then interpreted languages lose th
On Wed, Sep 12, 2007 at 10:15:50PM +0100, Claus Reinke wrote:
>
>
> >Aren't there ways of downloading whole websites onto your
> >local machine. Kind of "follow all links from but stop
> >when going outside of site ". I'm hopelessly ignorant
> >but this seems like something that must exist
Aren't there ways of downloading whole websites onto your
local machine. Kind of "follow all links from but stop
when going outside of site ". I'm hopelessly ignorant
but this seems like something that must exist
yes, and i was seriously considering writing a script for wget
to do that,
CTED] [mailto:[EMAIL PROTECTED]
| On Behalf Of Claus Reinke
| Sent: 12 September 2007 14:14
| To: Ian Lynagh
| Cc: cvs-ghc@haskell.org
| Subject: Re: regarding testsuite
|
| >>> - the usage documentation page is only online. it should be
| >>>copied into the download, for offline us
It's really just a proof-of-concept ATM, but I should mention
http://matrix.chaos.earth.li/~ian/diki/Index
home cooking!-)
I thought http://ikiwiki.info/ also supported a darcs backend, but its
webpage disagrees with me.
the details page (http://ikiwiki.info/rcs/details/) says
Support fo
* Python, being interpreted, makes a nicer language in which to make an
EDSL for this.
i'm not sure i buy that, but if there was truth in it, that ought to
change!-) nothing against python itself, but i thought the aim was to
get rid of dependencies, such as perl, rather than add them.
You
or, how about a separate repo for all the parts of the developer
wiki relevant to building, testing, hacking, and a cron job that
records and pushes from the wiki files nightly?
Ideally Trac would use darcs as its backend, and I could run a local Trac
against a local darcs repository of the dat
On Wed, Sep 12, 2007 at 02:43:57PM +0100, Simon Marlow wrote:
>
> Ideally Trac would use darcs as its backend, and I could run a local Trac
> against a local darcs repository of the data, and then push my changes when
> I'm online.
It's really just a proof-of-concept ATM, but I should mention
h
On Wed, Sep 12, 2007 at 03:03:11PM +0100, Simon Marlow wrote:
>
> The testsuite is an EDSL, as Ian pointed out. But you really don't want to
> have to compile the test descriptions against the testsuite driver code
> each time you change one, so you have to use the GHC API somehow.
I'd prefer no
Claus Reinke wrote:
but we're talking about testing ghc here, so we want to expose bugs.
it sounds like a bootstrap problem: write a small program that exercises
the low-level stuff needed for the main testsuite, and run that first:
if it works start the main suite of tests, otherwise, you've g
Claus Reinke wrote:
- the usage documentation page is only online. it should be
copied into the download, for offline users.
But then we have the problem of keeping it in sync.
that is exactly the problem your users run into, only aggravated
by not having the page in the first place. can't
- the usage documentation page is only online. it should be
copied into the download, for offline users.
But then we have the problem of keeping it in sync.
that is exactly the problem your users run into, only aggravated
by not having the page in the first place. can't the trak wiki push
th
- why do i need to install python to run haskell tests? isn't
haskell good enough (dogfood and all that..)?
A couple of reasons come to mind:
* The testsuite driver itself is actually a pretty good test of low
level stuff: forking, threads for timing out tests, etc. Both old GHC
(used to b
On Thu, Sep 06, 2007 at 01:46:59AM +0100, Claus Reinke wrote:
> i had my first encounter with the testsuite, and i thought you
> might be interested in first-encounter notes (platform: win/xp,
> cygwin shell, mingw gcc):-)
>
> - why do i need to install python to run haskell tests? isn't
>hask
i had my first encounter with the testsuite, and i thought you
might be interested in first-encounter notes (platform: win/xp,
cygwin shell, mingw gcc):-)
- why do i need to install python to run haskell tests? isn't
haskell good enough (dogfood and all that..)?
- when the testsuite is pulled
18 matches
Mail list logo
