Re: .NET approach -- MI400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

The main thing missing from our object strategy was inheritance. This
obscures some of the object properties we do have. When you have an API or
even a command that says "DLTPGM", you really have a member function, just
spelled awkwardly and with no inheritance. DLTPGM does not work on a file
by mistake, for example. If you had it in API form and passed it a system
pointer to a file object, it would say "wrong type". That's as enforceable
as any C++ or Java member function. Maybe more so.

IMHO, the MAIN thing missing is user-definable objects.

CL is such a great language because it is extensible (you can create your own
commands). Oh, that OS/400 would allow user-definable objects. That is,
PERSISTENT user-definable objects. Sure, we can emulate some of that using
user spaces, or other combinations of existing system objects. However, we
cannot fully encapsulate them since we must depend on existing (standalone)
system objects to access/modify/control them. We cannot make sure that
someone else won't WRKOBJ on one of our component objects and screw things up.

Michael Polutta
Atlanta, GA