[GRASS5] Thought on my CVS problem

Justin Hickey jhickey at hpcc.nectec.or.th
Mon Sep 18 03:25:12 EDT 2000


Hello Bernhard

Bernhard Reiter wrote:
> I see no reason why a good bison output should not be platform
> dependent. If it is, then we cannot bring the preconstructed files
> with the standard tarball.

OK, but how do we determine if it actually is platform independant? Do
we need to brute force test it on every platform? And then once we do
determine this, how do we manage these files so that what happened to me
(local machine generating a very different version) doesn't happen in
the future? Also, if a user compiles GRASS and a new different version
is generated, can we assume the new version produced a file that
contains all the features it is supposed to? Is there a way to prevent
local machines (that have bison and yacc installed) from generating
their own version? Is the .cvsignore file that was mentioned earlier the
answer?

The reason I'm asking all these questions is that I never worked with
lex or yacc except for simple assignments at university. So I don't know
the differences between the different versions and the implications of
using the locally generated files with regard to them reliably
performing the same functionality as the CVS version.

This is important to me since I will be changing a large number of files
when I upgrade GRASS to use the new environment system, and I would
really prefer to do a commit from the root of the CVS tree.

-- 
Sincerely,

Jazzman (a.k.a. Justin Hickey)  e-mail: jhickey at hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand
==================================================================
People who think they know everything are very irritating to those
of us who do.  ---Anonymous

Jazz and Trek Rule!!!
==================================================================

---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'



More information about the grass-dev mailing list