From: William S F. <ws...@fu...> - 2013-04-27 18:19:38
|
Can the Octave experts let me know how to get rid of these warnings which are appearing using octave 3.6.4: checking Examples/octave/callback warning: function ./example.oct shadows a core library function checking Examples/octave/class warning: function ./example.oct shadows a core library function I'm not sure what the name of the function it is shadowing, can we rename the function or suppress the warning? William |
From: Kris T. <kri...@gm...> - 2013-04-28 21:51:57
|
> From: William S Fulton > > Can the Octave experts let me know how to get rid of these warnings which > are appearing using octave 3.6.4: > > checking Examples/octave/callback > warning: function ./example.oct shadows a core library function > checking Examples/octave/class > warning: function ./example.oct shadows a core library function > > I'm not sure what the name of the function it is shadowing, can we rename > the function or suppress the warning? Hi William In my octave (3.6.1) (just launching octave, no swig involved), I get: octave:1> which example `example' is a function from the file /usr/local/share/octave/3.6.1/m/testfun/example.m This function is used to find examples in the documentation for a function (try "example example"). The naming is of course an unfortunate choice for a globally visible function, but I don't think there's anything that can be done about that. I'm not sure how to disable the warning (aside from renaming the example in swig of course). There's a thread on http://octave.1599824.n4.nabble.com/warn-when-core-functions-are-shadowed-td 1645710.html but the octave command line option suggested at the end hasn't been implemented yet (up to 3.6.1 anyway). Doing it in a .octave seems tricky (unless you do it before adding the path with the "swig" example). Kris |
From: Karl W. <kar...@gm...> - 2013-04-29 10:32:32
|
Hi William, I think the only reliable way around this would be to change the output Octave module name in Examples/octave/ to something else, e.g. swigexample. I think you'd just need to change the TARGET name in the Makefiles and then edit the runme.m scripts. Cheers, Karl On 27 April 2013 19:55, William S Fulton <ws...@fu...> wrote: > > Can the Octave experts let me know how to get rid of these warnings which > are appearing using octave 3.6.4: > > checking Examples/octave/callback > warning: function ./example.oct shadows a core library function > checking Examples/octave/class > warning: function ./example.oct shadows a core library function > > I'm not sure what the name of the function it is shadowing, can we rename > the function or suppress the warning? > > William > > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > _______________________________________________ > Swig-devel mailing list > Swi...@li... > https://lists.sourceforge.net/lists/listinfo/swig-devel > > |
From: William S F. <ws...@fu...> - 2013-04-30 06:56:27
|
Thanks for the diagnosis. Yes, let's change the name of the TARGET to swigexample. I'll do it in the next couple of days if no-one beats me to it. William On 29/04/13 11:31, Karl Wette wrote: > Hi William, > > I think the only reliable way around this would be to change the output > Octave module name in Examples/octave/ to something else, e.g. > swigexample. I think you'd just need to change the TARGET name in the > Makefiles and then edit the runme.m scripts. > > Cheers, > Karl > > > On 27 April 2013 19:55, William S Fulton <ws...@fu... > <mailto:ws...@fu...>> wrote: > > > Can the Octave experts let me know how to get rid of these warnings > which are appearing using octave 3.6.4: > > checking Examples/octave/callback > warning: function ./example.oct shadows a core library function > checking Examples/octave/class > warning: function ./example.oct shadows a core library function > > I'm not sure what the name of the function it is shadowing, can we > rename the function or suppress the warning? > > William > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring > service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! > http://p.sf.net/sfu/newrelic_d2d_apr > _______________________________________________ > Swig-devel mailing list > Swi...@li... > <mailto:Swi...@li...> > https://lists.sourceforge.net/lists/listinfo/swig-devel > > |
From: Karl W. <kar...@gm...> - 2013-05-08 20:47:37
|
Hi William, I've just opened a pull request for this: https://github.com/swig/swig/pull/46 Cheers, Karl On 30 April 2013 08:56, William S Fulton <ws...@fu...> wrote: > Thanks for the diagnosis. Yes, let's change the name of the TARGET to > swigexample. I'll do it in the next couple of days if no-one beats me to it. > > William > > > On 29/04/13 11:31, Karl Wette wrote: > >> Hi William, >> >> I think the only reliable way around this would be to change the output >> Octave module name in Examples/octave/ to something else, e.g. >> swigexample. I think you'd just need to change the TARGET name in the >> Makefiles and then edit the runme.m scripts. >> >> Cheers, >> Karl >> >> >> On 27 April 2013 19:55, William S Fulton <ws...@fu... >> <mailto:ws...@fu....**uk <ws...@fu...>>> wrote: >> >> >> Can the Octave experts let me know how to get rid of these warnings >> which are appearing using octave 3.6.4: >> >> checking Examples/octave/callback >> warning: function ./example.oct shadows a core library function >> checking Examples/octave/class >> warning: function ./example.oct shadows a core library function >> >> I'm not sure what the name of the function it is shadowing, can we >> rename the function or suppress the warning? >> >> William >> >> ------------------------------**------------------------------** >> ------------------ >> Try New Relic Now & We'll Send You this Cool Shirt >> New Relic is the only SaaS-based application performance monitoring >> service >> that delivers powerful full stack analytics. Optimize and monitor your >> browser, app, & servers with just a few lines of code. Try New Relic >> and get this awesome Nerd Life shirt! >> http://p.sf.net/sfu/newrelic_**d2d_apr<http://p.sf.net/sfu/newrelic_d2d_apr> >> ______________________________**_________________ >> Swig-devel mailing list >> Swi...@li...urceforge.**net <Swi...@li...> >> <mailto:Swig-devel@lists.**sourceforge.net<Swi...@li...> >> > >> https://lists.sourceforge.net/**lists/listinfo/swig-devel<https://lists.sourceforge.net/lists/listinfo/swig-devel> >> >> >> > |
From: William S F. <ws...@fu...> - 2013-05-08 21:57:18
|
Great, thanks. I've committed this. Probably we should change the examples in the html files to match too? William On 08/05/13 21:46, Karl Wette wrote: > Hi William, > > I've just opened a pull request for this: > > https://github.com/swig/swig/pull/46 > > Cheers, > Karl > > > On 30 April 2013 08:56, William S Fulton <ws...@fu... > <mailto:ws...@fu...>> wrote: > > Thanks for the diagnosis. Yes, let's change the name of the TARGET > to swigexample. I'll do it in the next couple of days if no-one > beats me to it. > > William > > > On 29/04/13 11:31, Karl Wette wrote: > > Hi William, > > I think the only reliable way around this would be to change the > output > Octave module name in Examples/octave/ to something else, e.g. > swigexample. I think you'd just need to change the TARGET name > in the > Makefiles and then edit the runme.m scripts. > > Cheers, > Karl > > > On 27 April 2013 19:55, William S Fulton > <ws...@fu... <mailto:ws...@fu...> > <mailto:ws...@fu....__uk > <mailto:ws...@fu...>>> wrote: > > > Can the Octave experts let me know how to get rid of these > warnings > which are appearing using octave 3.6.4: > > checking Examples/octave/callback > warning: function ./example.oct shadows a core library function > checking Examples/octave/class > warning: function ./example.oct shadows a core library function > > I'm not sure what the name of the function it is shadowing, > can we > rename the function or suppress the warning? > > William > > > ------------------------------__------------------------------__------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance > monitoring > service > that delivers powerful full stack analytics. Optimize and > monitor your > browser, app, & servers with just a few lines of code. Try > New Relic > and get this awesome Nerd Life shirt! > http://p.sf.net/sfu/newrelic___d2d_apr > <http://p.sf.net/sfu/newrelic_d2d_apr> > _________________________________________________ > Swig-devel mailing list > Swi...@li...urceforge.__net > <mailto:Swi...@li...> > <mailto:Swig-devel@lists.__sourceforge.net > <mailto:Swi...@li...>> > https://lists.sourceforge.net/__lists/listinfo/swig-devel > <https://lists.sourceforge.net/lists/listinfo/swig-devel> > > > > |
From: Karl W. <kar...@gm...> - 2013-05-08 22:11:51
|
You're right, the docs should be kept up to date too. I've just added an extra patch to the pull request doing just that. Cheers, Karl On 8 May 2013 23:57, William S Fulton <ws...@fu...> wrote: > Great, thanks. I've committed this. Probably we should change the examples > in the html files to match too? > > William > > > On 08/05/13 21:46, Karl Wette wrote: > >> Hi William, >> >> I've just opened a pull request for this: >> >> https://github.com/swig/swig/**pull/46<https://github.com/swig/swig/pull/46> >> >> Cheers, >> Karl >> >> >> On 30 April 2013 08:56, William S Fulton <ws...@fu... >> <mailto:ws...@fu....**uk <ws...@fu...>>> wrote: >> >> Thanks for the diagnosis. Yes, let's change the name of the TARGET >> to swigexample. I'll do it in the next couple of days if no-one >> beats me to it. >> >> William >> >> >> On 29/04/13 11:31, Karl Wette wrote: >> >> Hi William, >> >> I think the only reliable way around this would be to change the >> output >> Octave module name in Examples/octave/ to something else, e.g. >> swigexample. I think you'd just need to change the TARGET name >> in the >> Makefiles and then edit the runme.m scripts. >> >> Cheers, >> Karl >> >> >> On 27 April 2013 19:55, William S Fulton >> <ws...@fu... <mailto:ws...@fu....**uk<ws...@fu...> >> > >> <mailto:ws...@fu...._**_uk >> >> <mailto:ws...@fu....**uk <ws...@fu...>>>> >> wrote: >> >> >> Can the Octave experts let me know how to get rid of these >> warnings >> which are appearing using octave 3.6.4: >> >> checking Examples/octave/callback >> warning: function ./example.oct shadows a core library >> function >> checking Examples/octave/class >> warning: function ./example.oct shadows a core library >> function >> >> I'm not sure what the name of the function it is shadowing, >> can we >> rename the function or suppress the warning? >> >> William >> >> >> ------------------------------**__----------------------------** >> --__------------------ >> >> Try New Relic Now & We'll Send You this Cool Shirt >> New Relic is the only SaaS-based application performance >> monitoring >> service >> that delivers powerful full stack analytics. Optimize and >> monitor your >> browser, app, & servers with just a few lines of code. Try >> New Relic >> and get this awesome Nerd Life shirt! >> http://p.sf.net/sfu/newrelic__**_d2d_apr<http://p.sf.net/sfu/newrelic___d2d_apr> >> <http://p.sf.net/sfu/newrelic_**d2d_apr<http://p.sf.net/sfu/newrelic_d2d_apr> >> > >> ______________________________**___________________ >> Swig-devel mailing list >> Swi...@li...urceforge._**_net >> <mailto:Swig-devel@lists.**sourceforge.net<Swi...@li...> >> > >> <mailto:Swig-devel@lists.__sou**rceforge.net<http://sourceforge.net> >> <mailto:Swig-devel@lists.**sourceforge.net<Swi...@li...> >> >> >> https://lists.sourceforge.net/**__lists/listinfo/swig-devel<https://lists.sourceforge.net/__lists/listinfo/swig-devel> >> <https://lists.sourceforge.**net/lists/listinfo/swig-devel<https://lists.sourceforge.net/lists/listinfo/swig-devel> >> > >> >> >> >> >> > |