On Jul 30, 2005, at 20:21, Max Horn wrote:
Am 28.07.2005 um 19:48 schrieb Jack Howarth:
Still one has to ask exactly which compilers in the gcc4 package
we should be focusing on? The gfortran compiler specifically is
making
really good progress. With patches to be added today, it should pass
almost all of the NIST Fortran validation testsuite. I think we
would be
far better off doing the same thing for gfortran as we do for g95.
Sampling the source code at regular intervals. Since gcc 4.1 is into
stage 3, it is probably worthwhile testing that branch for gfortran
since most of the new features and fixes go into that branch first.
Better to help provide feedback now rather than to have to wait for
the 4.1.1 release.
A reason to package a patched release build or even a CVS version,
would
be to work around a known specific problem reported by a user, like a
crash etc.. Testing new features or improved standard compliance do
not
factor in there, IMO.
I basically agree with Peter and Max, unless other packages depend on
Fortran language's standard compliance. If other packages, mainly
scientific or engineering ones, had difficulties of building/running
caused by the inconsistent compliance of gfortran/g95, patched release
or CVS version would have meanings, and should be acceptable.
kinako
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Fink-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-devel
