Re: Quieter Monitors -- 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: Quieter Monitors
From: Rory Hewitt <rory.hewitt@xxxxxxxxx>
Date: Tue, 23 Feb 2010 09:21:04 -0800
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>

Vern,

If you have a removeMsgs() procedure which runs as soon as the error is
encountered, you wouldn't need a separate endMag() procedure, would you -
your removeMsgs() procedure would simply remove every message after the
startMsg() one...

Rory

On Tue, Feb 23, 2010 at 5:02 AM, Vern Hamberg <vhamberg@xxxxxxxxxxx> wrote:

Rory

I like the startMsg() - removeMsg() approach - I did the same thing with
3 functions, as I recall - an endMsg() being the bracketing function.

Vern

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Quieter Monitors , Vern Hamberg

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.