Re: Debugging MI code -- 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.

Subject: Re: [MI400] Debugging MI code
From: "Adrian Oprea" <aoprea@xxxxxxxxxxxxx>
Date: Tue, 2 Mar 2004 17:38:26 +0200
List-archive: <http://archive.midrange.com/mi400>
List-help: <mailto:mi400-request@midrange.com?subject=help>
List-id: MI Programming on the AS400 / iSeries <mi400.midrange.com>
List-post: <mailto:mi400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/mi400>, <mailto:mi400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/mi400>, <mailto:mi400-request@midrange.com?subject=unsubscribe>

> 
> Yes, and since it makes no allowances for the way C handles character
> strings (which, I freely admit, is more than a little bit meschuga, but
> PL/I would be my language of choice), you try to look at a character
> string variable, and you've got to go through all sorts of rigmarole to
> do it.

I always display strings in hex when debuging ILE C programs.

Adrian

As an Amazon Associate we earn from qualifying purchases.

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.