On Wed, Dec 5, 2012 at 12:39 PM, hakan <hexi...@users.sourceforge.net>wrote:
> Not agree here, a "compability flag" is as I see it a good choice.
> If you have a program that uses compabilitymode=1 (default) will run OK,
> as long as you don't want to use "new" stuff, that is at compabilitymode=2
> level (.singleSelection sample, just change mode to 2 in new program , old
> program still work as before unchanged (default mode = 1)
> other times if one want to utilize new "stuff" in old programs, because of
> changed/added functionallity to classes/routines/whatever, change old
> program to current mode level and change the old program to conform to that
> mode, if needed.
> New program choose on which mode it should be able to run 1....n.
> (probably always the latest)
> Benefits
> Old program will work asis at each compabilitymode level
> When changing old/new program change code to conform to latest mode at
> time.
> New programs will probably utilize lastest mode level, and when getting
> old they still run.on that level.
>
>
Yes, I agree with that in general. You put it pretty well.
I'm especially interested in this idea, because there are a number of
things in ooDialog I would like to fix, but don't know how to because of
backwards compatibility.
The zero-based indexes being a good example. Most of the stuff uses
one-based indexes, but then you hit something like the ListView that uses
zero-based indexes.
--
Mark Miesfeld
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
