Re: Coding subprocedures in CL -- MIDRANGE-L

× 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.

Subject: Re: Coding subprocedures in CL
From: rob@xxxxxxxxx
Date: Fri, 31 Oct 2014 11:32:34 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

There was awhile that I got so frustrated with CL that I pretty much
decided to decided to do it all in RPG and to heck with it. Granted, this
may have complicated things a bit. This
MYPROC PARM(...
MONMSG ...
may have turned into
CALL someApi
Check error code status
But I just had it with the lack of updates, subroutines, structure, etc in
CL.

Then the last few releases started changing my opinion...
But, the no local variables and whatnot is a bit frustrating.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Coding subprocedures in CL , Gary Thompson

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.