Re: Calling an ILE C Routine from ILE RPG (V7R2) -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Calling an ILE C Routine from ILE RPG (V7R2)
From: Javier Sanchez <javiersanchezbarquero@xxxxxxxxx>
Date: Fri, 22 May 2020 14:46:57 -0600
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@lists.midrange.com?subject=help>
List-id: RPG programming on IBM i <rpg400-l.lists.midrange.com>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

Based on the code that you point us to on GitHub, you should not need to

null-terminate the first parameter ("PW_BUF" in your prototype.)?? You
also should not define options(*String).

What options(*string) does is make a copy of your input parameter with
x'00' appended.? This isn't right in this case because you want to use
the PW_BUF parameter for output, and if the C code changes a copy of
your string, you'll never see the output.

Absolutely right! My suggestion was based on the assumption that he was
using a function like strlen() for example, which parameter is a const char*

JS

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2026 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.