Re: [Jmol-developers] Getting rid of 'dead code' warnings ?
Nico, Can you point to a specific piece of offending code? If the statements really are the syntax you are suggesting they make little sense. Jonathan On Aug 17, 2010, at 12:12 PM, Nicolas Vervelle wrote: > Hi, > > Could we get rid of the 'dead code' warnings ? > Most of them are due to code like : if (true || xxx) ... > which makes xxx a dead code. > > If it's intended, I see 2 ways of removing the warning : > Removing the dead code (if the true is definitive, it will clear it > definitely) > Replacing the 'true' by a constant (final static boolean) set to true : it > will be a lot more comprehensible and the compiler should stop to complain :) > Nico > > -- > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > ___ > Jmol-developers mailing list > Jmol-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jmol-developers Dr. Jonathan H. Gutow Chemistry Departmentgu...@uwosh.edu UW-Oshkosh Office: 920-424-1326 800 Algoma BoulevardFAX:920-424-2042 Oshkosh, WI 54901 http://www.uwosh.edu/facstaff/gutow -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Jmol-developers mailing list Jmol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-developers
Re: [Jmol-developers] Getting rid of 'dead code' warnings ?
I'll take a look... Bob On Tue, Aug 17, 2010 at 12:12 PM, Nicolas Vervelle wrote: > Hi, > > Could we get rid of the 'dead code' warnings ? > Most of them are due to code like : if (true || xxx) ... > which makes xxx a dead code. > > If it's intended, I see 2 ways of removing the warning : > >- Removing the dead code (if the true is definitive, it will clear it >definitely) >- Replacing the 'true' by a constant (final static boolean) set to true >: it will be a lot more comprehensible and the compiler should stop to >complain :) > > Nico > > > > -- > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > ___ > Jmol-developers mailing list > Jmol-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jmol-developers > > -- Robert M. Hanson Professor of Chemistry St. Olaf College 1520 St. Olaf Ave. Northfield, MN 55057 http://www.stolaf.edu/people/hansonr phone: 507-786-3107 If nature does not answer first what we want, it is better to take what answer we get. -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Jmol-developers mailing list Jmol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-developers
Re: [Jmol-developers] Getting rid of 'dead code' warnings ?
that pretty much does it... On Tue, Aug 17, 2010 at 12:12 PM, Nicolas Vervelle wrote: > Hi, > > Could we get rid of the 'dead code' warnings ? > Most of them are due to code like : if (true || xxx) ... > which makes xxx a dead code. > > If it's intended, I see 2 ways of removing the warning : > >- Removing the dead code (if the true is definitive, it will clear it >definitely) >- Replacing the 'true' by a constant (final static boolean) set to true >: it will be a lot more comprehensible and the compiler should stop to >complain :) > > Nico > > > > -- > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > ___ > Jmol-developers mailing list > Jmol-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jmol-developers > > -- Robert M. Hanson Professor of Chemistry St. Olaf College 1520 St. Olaf Ave. Northfield, MN 55057 http://www.stolaf.edu/people/hansonr phone: 507-786-3107 If nature does not answer first what we want, it is better to take what answer we get. -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Jmol-developers mailing list Jmol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-developers
Re: [Jmol-developers] Getting rid of 'dead code' warnings ?
Hi, Bob fixed the most obvious, here are the outstanding warnings for dead code : DescriptionResourcePathLocationType Dead codeJmolApp.java/Jmol/src/org/openscience/jmol/appline 372Java Problem Dead codeJvxl.java/Jmol/src/org/openscience/jvxlline 283Java Problem Dead codeJvxl.java/Jmol/src/org/openscience/jvxlline 313Java Problem Dead codeMesh.java/Jmol/src/org/jmol/shapeline 241Java Problem Dead codeScriptMathProcessor.java/Jmol/src/org/jmol/scriptline 196Java Problem Dead codeScriptMathProcessor.java/Jmol/src/org/jmol/scriptline 205Java Problem Dead codeSimplePopup.java/Jmol/src/org/jmol/popupline 400 Java Problem Nico On Tue, Aug 17, 2010 at 11:44 PM, Jonathan Gutow wrote: > Nico, > Can you point to a specific piece of offending code? If the statements > really are the syntax you are suggesting they make little sense. > > Jonathan > On Aug 17, 2010, at 12:12 PM, Nicolas Vervelle wrote: > > Hi, > > Could we get rid of the 'dead code' warnings ? > Most of them are due to code like : if (true || xxx) ... > which makes xxx a dead code. > > If it's intended, I see 2 ways of removing the warning : > >- Removing the dead code (if the true is definitive, it will clear it >definitely) >- Replacing the 'true' by a constant (final static boolean) set to true >: it will be a lot more comprehensible and the compiler should stop to >complain :) > > Nico > > > -- > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > ___ > Jmol-developers mailing list > Jmol-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jmol-developers > > > Dr. Jonathan H. Gutow > Chemistry Departmentgu...@uwosh.edu > UW-Oshkosh Office: 920-424-1326 > 800 Algoma BoulevardFAX:920-424-2042 > Oshkosh, WI 54901 > http://www.uwosh.edu/facstaff/gutow > > > > -- > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > ___ > Jmol-developers mailing list > Jmol-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jmol-developers > > -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Jmol-developers mailing list Jmol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-developers
Re: [Jmol-developers] Getting rid of 'dead code' warnings ?
If I coming in Ghent and I live an a Hostel for 3-4 days, it's possible to find? Or I have the same chances (internet). -- MSc. Apopei Andrei Ionut > andrei.apo...@geology.uaic.ro Al. I. Cuza University, Department of Geology Carol I st. 11, 700506, Iasi, ROMANIA Romanian Database of Raman Spectroscopy From: Nicolas Vervelle To: jmol-developers@lists.sourceforge.net Sent: Wed, August 18, 2010 8:11:22 PM Subject: Re: [Jmol-developers] Getting rid of 'dead code' warnings ? Hi, Bob fixed the most obvious, here are the outstanding warnings for dead code : DescriptionResourcePathLocationType Dead codeJmolApp.java/Jmol/src/org/openscience/jmol/appline 372 Java Problem Dead codeJvxl.java/Jmol/src/org/openscience/jvxlline 283Java Problem Dead codeJvxl.java/Jmol/src/org/openscience/jvxlline 313Java Problem Dead codeMesh.java/Jmol/src/org/jmol/shapeline 241Java Problem Dead codeScriptMathProcessor.java/Jmol/src/org/jmol/scriptline 196Java Problem Dead codeScriptMathProcessor.java/Jmol/src/org/jmol/scriptline 205Java Problem Dead codeSimplePopup.java/Jmol/src/org/jmol/popupline 400Java Problem Nico On Tue, Aug 17, 2010 at 11:44 PM, Jonathan Gutow wrote: Nico, >Can you point to a specific piece of offending code? If the statements really >are the syntax you are suggesting they make little sense. > > >Jonathan > >On Aug 17, 2010, at 12:12 PM, Nicolas Vervelle wrote: > >Hi, >> >>Could we get rid of the 'dead code' warnings ? >>Most of them are due to code like : if (true || xxx) ... >>which makes xxx a dead code. >> >>If it's intended, I see 2 ways of removing the warning : >> >> * Removing the dead code (if the true is definitive, it will clear it >>definitely) >> * Replacing the 'true' by a constant (final static boolean) set to true >> : it >>will be a lot more comprehensible and the compiler should stop to complain >>:)Nico >> >> -- >>This SF.net email is sponsored by >> >>Make an app they can't live without >>Enter the BlackBerry Developer Challenge >>http://p.sf.net/sfu/RIM-dev2dev >>___ >>Jmol-developers mailing list >>Jmol-developers@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/jmol-developers >> > > Dr. Jonathan H. Gutow >Chemistry Departmentgu...@uwosh.edu >UW-Oshkosh Office: 920-424-1326 >800 Algoma BoulevardFAX:920-424-2042 >Oshkosh, WI 54901 >http://www.uwosh.edu/facstaff/gutow > >-- >This SF.net email is sponsored by > >Make an app they can't live without >Enter the BlackBerry Developer Challenge >http://p.sf.net/sfu/RIM-dev2dev >___ >Jmol-developers mailing list >Jmol-developers@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/jmol-developers > > -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Jmol-developers mailing list Jmol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-developers
Re: [Jmol-developers] Getting rid of 'dead code' warnings ?
ohhh sorry, a wrong reply :( -- MSc. Apopei Andrei Ionut > andrei.apo...@geology.uaic.ro Al. I. Cuza University, Department of Geology Carol I st. 11, 700506, Iasi, ROMANIA Romanian Database of Raman Spectroscopy From: Nicolas Vervelle To: jmol-developers@lists.sourceforge.net Sent: Wed, August 18, 2010 8:11:22 PM Subject: Re: [Jmol-developers] Getting rid of 'dead code' warnings ? Hi, Bob fixed the most obvious, here are the outstanding warnings for dead code : DescriptionResourcePathLocationType Dead codeJmolApp.java/Jmol/src/org/openscience/jmol/appline 372 Java Problem Dead codeJvxl.java/Jmol/src/org/openscience/jvxlline 283Java Problem Dead codeJvxl.java/Jmol/src/org/openscience/jvxlline 313Java Problem Dead codeMesh.java/Jmol/src/org/jmol/shapeline 241Java Problem Dead codeScriptMathProcessor.java/Jmol/src/org/jmol/scriptline 196Java Problem Dead codeScriptMathProcessor.java/Jmol/src/org/jmol/scriptline 205Java Problem Dead codeSimplePopup.java/Jmol/src/org/jmol/popupline 400Java Problem Nico On Tue, Aug 17, 2010 at 11:44 PM, Jonathan Gutow wrote: Nico, >Can you point to a specific piece of offending code? If the statements really >are the syntax you are suggesting they make little sense. > > >Jonathan > >On Aug 17, 2010, at 12:12 PM, Nicolas Vervelle wrote: > >Hi, >> >>Could we get rid of the 'dead code' warnings ? >>Most of them are due to code like : if (true || xxx) ... >>which makes xxx a dead code. >> >>If it's intended, I see 2 ways of removing the warning : >> >> * Removing the dead code (if the true is definitive, it will clear it >>definitely) >> * Replacing the 'true' by a constant (final static boolean) set to true >> : it >>will be a lot more comprehensible and the compiler should stop to complain >>:)Nico >> >> -- >>This SF.net email is sponsored by >> >>Make an app they can't live without >>Enter the BlackBerry Developer Challenge >>http://p.sf.net/sfu/RIM-dev2dev >>___ >>Jmol-developers mailing list >>Jmol-developers@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/jmol-developers >> > > Dr. Jonathan H. Gutow >Chemistry Departmentgu...@uwosh.edu >UW-Oshkosh Office: 920-424-1326 >800 Algoma BoulevardFAX:920-424-2042 >Oshkosh, WI 54901 >http://www.uwosh.edu/facstaff/gutow > >-- >This SF.net email is sponsored by > >Make an app they can't live without >Enter the BlackBerry Developer Challenge >http://p.sf.net/sfu/RIM-dev2dev >___ >Jmol-developers mailing list >Jmol-developers@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/jmol-developers > > -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Jmol-developers mailing list Jmol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-developers
