I decided to download glpk and try it on Solaris.
I was going to congratulate you on there being no warnings messages from
the compiler, then thought I'd suggest the -Wall flag was added if the
compiler was the GNU one.
But then I see that any warnings are thrown to /dev/null
e.g.
gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT glpipp01.lo -MD
-MP -MF .deps/glpipp01.Tpo -c glpipp01.c -o glpipp01.o >/dev/null 2>&1
Personally I'd like to see all errors reported, not copied to /dev/null.
Sorry, I realised it was probably not you that wrote the glpk package,
and so it is not you throwing warnings to /dev/null.
But IMHO it would be worth removing the junk that throws warnings away,
then see what warnings there are on each OS and fix them. There seems to
be a few packages in Sage that hide warning messages - I'm not so sure
its a good idea to add more that do this.
I'm not a mathematician, don't have a clue what this does, so I am
probably looking at this from a very different point of view to most.
But I don't think it's a good idea to include code that hides warnings.
Again, it's a personal thing but when I look at web sites, like Wolfram
Research's, which has 42 errors:
it always makes me wonder how seriously quality is taken.
In contrast the Sage site has zero errors:
Mathematicians I've worked worth have always paid a lot of attention to
detail - far more than I think engineers tend to. If someone covers up
their compiler errors, it makes me wonder whether sufficient attention
to detail is applied elsewhere.
If someone like WRI, Maplesoft etc wanted to try to point out the
disadvantages of Sage, showing how we hide warnings would be like giving
them ammunition to blow us up with.
I'm sure a lot of people will disagree with me, but personally I would
avoid adding things to sage that rely on code that is built like that.
Dave
There is also a more recent GLPK spkg at http://trac.sagemath.org/sage_trac/ticket/6602 , I believe.
-Willem Jan
On Sat, Aug 1, 2009 at 9:32 AM, Marshall Hampton<hamp...@gmail.com> wrote:
>
> I got from Minh's comment:
>
> "Once #6502 gets positive review, this SPKG could then be merged in
> the Sage standard packages repository."
That was a typo on my part. It should be "optional" instead of
"standard". My apology for any inconveniences caused.
--
Regards
Minh Van Nguyen