Re: w32feature()

new topic     » goto parent     » topic index » view thread      » older message » newer message

CChris wrote:
...
> > > I'm contemplting the addition of a w32feature(name) or
> > > w32feature(name,state=on)
> > > procedure that would act a little like a with/without directive in this
> > > regard.
...
> > > CChris
...
> > Arthur Crump wrote:
> > I would like to suggest w32feature(<version>,state=on)
> > to include ALL the features of the specified version.
...

> Interesting, but not quite practical.
> If "feature" includes any new stuff, then you have a simpler way, which is to
> keep the older version. If the scope is restricted to changes, welll that
> becomes
> more feasible.
> I don't think I'd go through the change log to rebuild all layers of change,
> including from a recent date. Were you implying this?
> 
> CChris

I had not thought about the implications of backdating it to early versions.
I agree: that would not be feasible.  Even if new additions could be flagged
as belonging to a specific version, the earlier additions could make nonsense of
it.
Probably the earliest version that could be set may be the version with
feature().
This could lead some programmers to the requirement to use two or more versions,
depending upon the application.
The thread 'EuDir and EuInc' could suggest how to do this.

Arthur Crump
I have been programming for nearly fifty years but only for three in Euphoria.
I have not contributed to the archive so my input does not have much value.

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu