Can someone give me some reference for OOPS concept of Open Edge 11?
This question makes me wonder if you tried to read the documentation.
This first time I hear Oops for OOP :-)
Me too. I thought I was being dense not knowing what the S stood for.
In case you're attending the PUG Challenge Americas conference later this month, you might want to attend my session OO-Oh on basic OO concepts in ABL.
>>> [Mike Fechner's ] session OO-Oh on basic OO concepts in ABL.
Past iterations of this talk have always been educational.
and, potentially, [View:https://community.progress.com/community_groups/openedge_general/w/openedgegeneral/2743.openedge-11-6-product-documentation:550:50]
OOPS: Object Orientated Programming Structure.
Don't forget Pseudo Object Oriented Programming (aka "Smart Objects"...) ;)
>>> Hey, that was the best we’ve had two decades ago.
Hey.... we tried our best.
Actually, maybe SmartObjects are best described as "Oops!", and we can use OOP for the clever (smarter) new ABL features. :-)
I think of smart objects as fertilizer for the OOP features that we now have :)
>>> smart objects as fertilizer for the OOP
I am taking that as a complement (and trying to avoid enunerating all the synonyms for "fertilizer" that I can think of.)
But seriously, this was patentable by Progress (Patent # 6,003,037), and I like to note that it has been referenced over 100 times in other patents.
Smartalec acronyms aside... of course it is a compliment! I have always advocated that Progress get experience actually using the language to build stuff. IMHO the experience gained from building Smart Objects was invaluable in helping you guys understand what we needed for the OO4GL.
... and ProDatasets.
I'm not sure why you would call it an "oops". It was/is cool technology (like the Web Client and WebSpeed).
>>> I'm not sure why you would call it an "oops".
Sorry. I was being a little tongue-in-cheek, and riffing on the title of this thread (OOPS Concepts in the ABL).
While it would have been wonderful to have done SmartObjects on top of OOABL, we did some pretty impressive things in SmartOjects using a prototype/delegation model and persistent procedures. I was recently looking at the code, and it also took advantage significantly of the ABL preprocessor as a way to get general purpose routines that would compile to 'bound' specific class definitions (on an "Abstract" template).
If anyone has a "SmartPerson" t-shirt, I remember those fondly, and would love to see a picture.