On 2/26/2013 4:50 PM, Vladimir Panteleev wrote:
On Sunday, 3 February 2013 at 00:37:55 UTC, David Nadlinger wrote:
1) Provide an Open Source clean-room implementation of response_expand, the
function the DMD frontend uses to parse response files. Unfortunately, it is
under the copyright belongs
On 2/3/2013 6:52 PM, David Nadlinger wrote:
I want to avoid getting in touch with any non-free compiler code as much as
possible as Walter generally seems very conscious of licensing issues and I
don't want to jeopardize the future of LDC.
Having D be IP-clean is essential to the future of D.
On 2/3/2013 6:31 PM, David Nadlinger wrote:
It's not like we realistically have to be afraid of Symantec suing anybody over
that piece of code, but ideally Walter would be able to accept that rewritten
piece of code back into DMD without having to fear any licensing issues.
It's more about doin
On Sunday, 3 February 2013 at 00:37:55 UTC, David Nadlinger wrote:
1) Provide an Open Source clean-room implementation of
response_expand, the function the DMD frontend uses to parse
response files. Unfortunately, it is under the copyright
belongs (partly?) to Symantec, so Walter can't simply
On Sunday, 3 February 2013 at 14:51:59 UTC, Danny Arends wrote:
Perhaps I should create an requirements outline after reading
the source:
This would be great!
I want to avoid getting in touch with any non-free compiler code
as much as possible as Walter generally seems very conscious of
lice
On Sunday, 3 February 2013 at 15:07:50 UTC, Dicebot wrote:
On Sunday, 3 February 2013 at 14:51:59 UTC, Danny Arends wrote:
Perhaps I should create an requirements outline after reading
the source:
From the post David links to:
"2) Could somebody read the source and document the quirks of
the
Am 03.02.2013 17:53, schrieb Joseph Rushton Wakeling:
On 02/03/2013 05:33 PM, Paulo Pinto wrote:
Someone needs to write it, hence David's request.
I thought David's request was for an implementation, not a spec!
There's little point for those of us who haven't seen the original code
to go and
On 02/03/2013 05:33 PM, Paulo Pinto wrote:
Someone needs to write it, hence David's request.
I thought David's request was for an implementation, not a spec! There's little
point for those of us who haven't seen the original code to go and look at it to
write a spec, when it merely takes awa
Am 03.02.2013 16:33, schrieb Joseph Rushton Wakeling:
On 02/03/2013 03:17 PM, jerro wrote:
AFAIK "clean room implementation" means reimplementing it without
looking at the
source code of the original implementation.
So, is there spec for what it should do?
Someone needs to write it, hence D
On 02/03/2013 03:17 PM, jerro wrote:
AFAIK "clean room implementation" means reimplementing it without looking at the
source code of the original implementation.
So, is there spec for what it should do?
On Sunday, 3 February 2013 at 14:51:59 UTC, Danny Arends wrote:
Perhaps I should create an requirements outline after reading
the source:
From the post David links to:
"2) Could somebody read the source and document the quirks of
the
parser in painstaking detail, so that somebody else can do
Perhaps I should create an requirements outline after reading the
source:
From the post David links to:
"2) Could somebody read the source and document the quirks of the
parser in painstaking detail, so that somebody else can do a
clean room implementation?"
Gr,
Danny
How is anyone supposed to know what it does then ??
Also any new code needs to satisfy/adhere to the current
interface,
so it would be pretty useless not knowing what that is
Furthermore to replace you need to know what to return on error /
success
Gr,
On Sunday, 3 February 2013 at 14:17:1
How should such a clean room implementation look like ??
Does the structure need to change ??
Is it enough to rewrite the code in D ??
Should the code be in C if so how much change ??
AFAIK "clean room implementation" means reimplementing it without
looking at the source code of the ori
1) Provide an Open Source clean-room implementation of
response_expand, the function the DMD frontend uses to parse
response files. Unfortunately, it is under the copyright
belongs (partly?) to Symantec, so Walter can't simply
re-license it for use in GDC/LDC, where it is needed to provide
DM
Hi all,
in case you have an afternoon or two to spare, here are two ideas
how you could help with D compiler development (DMD/GDC/LDC):
1) Provide an Open Source clean-room implementation of
response_expand, the function the DMD frontend uses to parse
response files. Unfortunately, it is
http://d.puremagic.com/test-results/
Oops, I think I had a "brain fart".
The compiler is written in C++, but the executable is DMD which
compiles D code, which allows unit testing.
I was not being critical of D development, I was just curious.
BTW - I am the guy that started the discussion on creating a
subset of D called "D-" or "embedded D", i.e. D without garbage
collection.
D for the low resource, 32 bit microcontroller world.
I guess I was just trying to put "my 2
James Miller:
and most people don't have the compiler
suddenly pull the rug from underneath them (unless they were
relying on the buggy behaviour).
Relying on "buggy behavior" (or on deprecated features) is not
rare. An example:
http://d.puremagic.com/issues/show_bug.cgi?id=7736
Fixing thi
On Mon, Apr 02, 2012 at 12:02:56AM +0200, foobar wrote:
[...]
> Regarding DMD - Walter has a test suite for it for the same purpose.
> I don't know the specifics of it as I never looked at it and not even
> sure whether it's open source or not. The core devs would be able to
> provide more specific
On 2 April 2012 10:02, foobar wrote:
> Or in other words you did regression testing.
>
> Regarding DMD - Walter has a test suite for it for the same purpose. I don't
> know the specifics of it as I never looked at it and not even sure whether
> it's open source or not. The core devs would be able
On Sunday, 1 April 2012 at 21:26:44 UTC, Tim Krimm wrote:
What is the process for developing the dmd compiler?
Years ago, when I worked on the IBM PLX/PLAS compiler, we had a
large collection of test case files.
We would create two executable versions of the compiler.
One executable was the "go
What is the process for developing the dmd compiler?
Years ago, when I worked on the IBM PLX/PLAS compiler, we had a
large collection of test case files.
We would create two executable versions of the compiler.
One executable was the "good" version and the other version was
the 'GOOD' version wi
24 matches
Mail list logo
