This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Ada policy
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: mrs at apple dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 30 Aug 04 19:03:39 EDT
- Subject: Re: Ada policy
Don't start fixing a testcase until after you've trimmed the testcase
down, then you will find that all bugs you fix will have cut down test
cases.
As I'm sure you know, if you start with copyrighted code and "trim it
down", you still have copyrighted code. Making a non-proprietary
version of a test case involves a lot more work than that.
We can describe the procedure to transform a proprietary testcase in
detail into one that isn't, if you want.
Let's not get into copyright law, but the point is that if you transform
it using a "procedure", it's still proprietary.
So, I guess I am confused as to, do you just not want to do the work
to produce the testcases, or do you lack the understanding of how to
do it?
There are a lot of people fixing bugs in the Ada front end. The skill levels
of each of these people in making non-proprietary versions of test cases
differs. The amount of time each has to commit to that work differs.
As Robert said, there will be lots of situations where the choice is either
to submit the fix without a test case or not submit the fix. Which do
you think is the best approach?