Re: TCP Connection Status & Socket Read -- RPG400-L

Subject: Re: TCP Connection Status & Socket Read
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Thu, 19 Jul 2007 21:29:48 -0400
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <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>

Joe Pluta wrote:

... But to be thorough, there is still the issue that large fields will NOT
work with a hardcoded "2". If the field is ever changed to be longer than
64K, then code that uses "2" will break.

True, but that would be the case no matter how the VARYING > 65535 was handled. The programmer who changes the length over the 65535 mark and gets an immediate syntax checker or compiler diagnostic about VARYING(4) being required has a better (imo) chance of spotting this problem when they do their impact analysis. If the compiler silently defaulted to VARYING(4), the programmer might be less aware of the extra impact analysis required due to the change in both the length and the prefix length.

Follow-Ups:

RE: TCP Connection Status & Socket Read , Joe Pluta

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.