On Fri, 26 Feb 2016 16:04:32 + Mike Blumenkrantz
said:
> On Fri, Feb 26, 2016 at 9:31 AM Carsten Haitzler
> wrote:
>
> > On Wed, 24 Feb 2016 22:52:52 + Mike Blumenkrantz
> > said:
> >
> > > I am trying to avoid using the efl version defines because they don't
> > > indicate if it's the
On Fri, 26 Feb 2016 14:57:06 + Andrew Williams said:
> Hypothetical of course but what about bug fix workarounds?
> I.e behave like x instead of y if >1.7 < 1.7.3
> Or requiring 1.10.1 as something didn't work right on the first release of
> the feature?
hypothetical ... and given point rele
On Fri, Feb 26, 2016 at 9:31 AM Carsten Haitzler
wrote:
> On Wed, 24 Feb 2016 22:52:52 + Mike Blumenkrantz
> said:
>
> > I am trying to avoid using the efl version defines because they don't
> > indicate if it's the prerelease from git, meaning that the features
> aren't
> > usable until the
Hypothetical of course but what about bug fix workarounds?
I.e behave like x instead of y if >1.7 < 1.7.3
Or requiring 1.10.1 as something didn't work right on the first release of
the feature?
Andy
On Fri, 26 Feb 2016 at 14:31, Carsten Haitzler wrote:
> On Wed, 24 Feb 2016 22:52:52 + Mike B
On Wed, 24 Feb 2016 22:52:52 + Mike Blumenkrantz
said:
> I am trying to avoid using the efl version defines because they don't
> indicate if it's the prerelease from git, meaning that the features aren't
> usable until the release occurs; not very helpful if I want a feature to be
> active no
Just bear in mind that the demo fails for 2.1 etc. I wonder if it would be
worth adding a macro like EFL_VERSION_MIN(1, 18)
Or as Mike points out (1, 17, 99).
Andy
On Wed, 24 Feb 2016 at 22:49, Carsten Haitzler wrote:
> On Wed, 24 Feb 2016 17:44:42 + Mike Blumenkrantz
> said:
>
> > It's po
I am trying to avoid using the efl version defines because they don't
indicate if it's the prerelease from git, meaning that the features aren't
usable until the release occurs; not very helpful if I want a feature to be
active now when it's supported.
It seems like this should be something availa
On Wed, 24 Feb 2016 17:44:42 + Mike Blumenkrantz
said:
> It's possible to #define constants in embryo, such as ones used for version
> checking. I haven't found any reference for how to detect them in a script,
> however. Any #if directive gets handled by epp during edje compilation, and
> us
