On Thu, 26 Nov 2009, Brian Hays wrote:
Hi Brian,
> The addition of specific "sub-rdds" of ADSCDX etc. came years later.
> I, and I imagine a lot of other people who started using rddads
> early on, never had a need to explicitly use those other rdds by name.
Any one who has code like:
proc copy_table( cSrc, cSrcRDD, cDst, cDstRDD )
use (cSrc) via (cSrcRDD)
copy to (cDst) via (cDstRDD)
return
designed to work with different RDDs in Clipper, needs ADS* RDDs to port
his code without introducing unnecessary and incompatible with other RDDs
modifications which are necessary to make working code like:
copy_table( "sales", "ADSCDX", "sales2", "ADSADT" )
In fact "ADS" RDD can be safely removed because the only one reason
to keep it are user habbits but ADS* RDDs cannot be removed without
reducing important functionality - working VIA clause in different
command/functions which allows to easy switch between RDDs.
> Are you suggesting that we should now have to re-write our apps by
> converting ADS to ADSADT? But wait: IIRC (I'm not sure),
> ADSCDX is the DEFAULT for ADS, so converting it to ADT doesn't
> really make sense, does it?
> If you're suggesting a change that would require people to change
> code that's been growing for 9 years, there needs to be a stronger
> reason to force the change than just compatibility with other rdds,
> IMHO.
> Or am I missing something?
Mindaugas wants to change only "ADT" RDD to "ADSADT" and you are not
using it so it's not a problem for you.
Anyhow you wrote that it's 9 years code.
In the past I left "ADS" RDD only for backward compatibility:
2005-09-02 20:10 UTC+0200 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
+ register ADS as three separate RDDs: ADSNTX, ADSCDX, ADT
(ADS RDD left for backward compatibility) - they do not
need to set table type.
so in fact you had over four years to update your code.
This suggests that forcing some modification immediately is better
because four years ago it was only 5 years code ;-)
Was it my mistake that I left "ADS" RDD?
best regards,
Przemek
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
