Re: Default extproc syntax not recognized by content assist -- WDSCI-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: Default extproc syntax not recognized by content assist
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Tue, 16 Apr 2019 17:33:19 -0400
List-archive: <https://archive.midrange.com/wdsci-l/>
List-help: <mailto:wdsci-l-request@lists.midrange.com?subject=help>
List-id: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l.lists.midrange.com>
List-post: <mailto:wdsci-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/wdsci-l>, <mailto:wdsci-l-request@lists.midrange.com?subject=unsubscribe>

On 2019-04-16 4:27 PM, Joe Pluta wrote:

Thanks, Barbara!

I'm not sure about the definition of "can't". EXT, EXTPGM and EXTPROC can all be coded without a parameter, and they default to the name of the RPG definition (uppercase).

True for EXTPGM and EXT, but I get an error from the compiler for EXTPROC without a parameter.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Default extproc syntax not recognized by content assist , Joe Pluta

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.