On Tue, Oct 16, 2012 at 11:06 AM, Benoît Minisini <gam...@users.sourceforge.net> wrote: > Hi, > > In the last revision, I added a new component 'gb.args', which replaces > the unmaintained 'gb.option'. By the way, does anyone use 'gb.option'? yep. Code can be moved across without too much work, but it creates a problem as it means we need to use the latest gambas, which is hard (debian is still on 3.1, for example)
Is there any way to detect at runtime (or compile-time) which module is available so both can supported? or can gb.option stay in the codebase for a little while (say six months) to enable transition Ian ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
