Re: CALL with optional parameters -- RPG400-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: CALL with optional parameters
From: Rory Hewitt <roryhewitt@xxxxxxxxx>
Date: Tue, 18 Aug 2009 10:44:20 -0700
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Oops. Very true. That's what happens when you write code without thinking
too hard :)

On Tue, Aug 18, 2009 at 9:49 AM, DeLong, Eric <EDeLong@xxxxxxxxxxxxxxx>wrote:

Rory,

I don't think your case statement will evaluate correctly... You should
start with "%parms > 9" and work your way down... As written, case will
always select the first clause, since this will always evaluate to true
whenever %parms > 2....

-Eric DeLong

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: CALL with optional parameters , Jerry Adams

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.