[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Storing generated files (was: Re: Make cvs ignore some changes in fi

From: Mike Ayers
Subject: Re: Storing generated files (was: Re: Make cvs ignore some changes in files)
Date: Thu, 22 Aug 2002 17:48:42 -0700
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721

Noel Yap wrote:
--- Mike Ayers <address@hidden> wrote:

        2)  The generation will not necessarily produce the
same result. A good example is lex/flex and yacc/bison generation. Lex and yacc are different tools on most of the machines on which they occur, yet tend to produce better (and, as I recall, more portable(?!)) results than flex/bison on those systems. A project I worked on would generate files using lex/yacc on a specific platform and archive them into the sources. Those building the project would compile, and most would get satisfactory results. Those who did not could clean out the generated files and rebuild; this usually worked. We could not require generation of these files, as not all systems had
lex/yacc or flex/bison.

IMHO, this isn't good CM.  If you want developers to
use the same generated file, they should be using the
same generation tool.

Errr, we wanted developers to use a generated file that *worked*. This is not the same file on all platforms, but a file needed to be generated for at least those platforms for which the tool is not available. The others could use that file or generate their own.

>  If this isn't possible, it
> becomes case 3) below.

Agreed - it's a corner case of several legitimate generation tools existing, none of which are available on all platforms.

I'm pretty sure there's nothing non-deterministic in
the computer world (except maybe for some cryto
hardware) so I'll assume you couldn't think of a
better word (nor can I).

You mean nondeterministic in the strict sense - I meant it in the CM sense of "the same input files yield the same output files". Strictly speaking, Mr. Andersson's problem can be put in this class.

Anyway, I can't comment on the compiler since I'm not
familiar with it.

Neither am I really. However, I should correct myself - it is the Xilinx compiler, not Altera, that has this "feature".

As for a random seed for testing, I'd say this is the
same as using vi (and manual typing) or recording a
feed to generate the data file.  If it's used for
testing, the file shouldn't be changing that often.

Yes, but many testers (myself included) would insist that the test set (file) be generated by the same tools that will power the end use. In any case, we don't disagree on the CM issues here.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]