Jeff's question about "why with C_OBJECT but not with BLOBs and pictures"
got me thinking a bit. Yeah, fair point. I can see in a language with no
pointer-like features why you would work things the way C_OBJECT works.
Personally, I like the explicit pointer syntax and find it helpful to be
reminded very clearly when I'm dealing with something indirectly.
So why did 4D abandon this for their
ref-counting-with-automatic-garbage-collection-but-who-really-knows-what-scope-means-now?
Haven't a clue. I can think up a bunch of different possibilities, ranging
across all positions on the Tech Ideas Continuum:
|____________|______________|______________|____________________|
Monsters! Eh? M'eh
Nice one Geniuses!
You'll have to ask 4D France to explain, if they're willing.
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
