Re: [sage-support] Warning messages when compiling 'lcalc'

2010-06-15 Thread Anne Driver
Professor Stein, you are completely missing the point. Any serious attempt to check source code would include in a thorough check of what variables are used, their types, what they are used for, how they are used, what (if any) values they are initialized to. That would be true whether you were lo

Re: [sage-support] Warning messages when compiling 'lcalc'

2010-06-08 Thread Dr. David Kirkby
On 06/ 8/10 08:38 PM, Michael Rubinstein wrote: The antiquated header files and unused variables have been removed in L-1.3, which has not yet been released to the public. It should be released in the next couple of weeks. Best, Mike It would be good if you could remove that option from your

Re: [sage-support] Warning messages when compiling 'lcalc'

2010-06-08 Thread Michael Rubinstein
The antiquated header files and unused variables have been removed in L-1.3, which has not yet been released to the public. It should be released in the next couple of weeks. Best, Mike On Tue, 8 Jun 2010, William Stein wrote: On Tue, Jun 8, 2010 at 12:21 PM, Anne Driver wrote: When buildi

Re: [sage-support] Warning messages when compiling 'lcalc'

2010-06-08 Thread William Stein
On Tue, Jun 8, 2010 at 12:21 PM, Anne Driver wrote: > When building open-source software, it is not unusual to see a few compiler > warnings - usually deprecated code. There's quite a lot of them in Sage. > > But looking at lcalc, the code seems particularly poor, with lots of unused > variables &

[sage-support] Warning messages when compiling 'lcalc'

2010-06-08 Thread Anne Driver
When building open-source software, it is not unusual to see a few compiler warnings - usually deprecated code. There's quite a lot of them in Sage. But looking at lcalc, the code seems particularly poor, with lots of unused variables & deprecated code. It does not exactly inspire confidence in Sa