× 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.



JMHO, but I think it depends. <g>  If the offsets are fixed, I'd go with the
data structure because it documents the layout of the information.  If
you're substringing the data out, it seems to me you need to comment what
you're doing.  I'd probably comment the data structure use too because of my
short term memory problem.  <g>

I'd only use substringing when the offsets aren't fixed and you have to
write code to find them.

Is this a topic where faith is an issue?  Don't think I've seen it before.
<g>

> -----Original Message-----
> From: Feador, Jerry [mailto:JFeador@Kiausa.com]
> Sent: Tuesday, June 18, 2002 8:37 AM
> To: 'rpg400-l@midrange.com'
> Subject: Field Parsing Style
>
>
> Hi All,
>
> Just a style question.
>
> The "standards" here say to always use a Data Structure to
> parse a field,
> yet I think it's more explanatory, at the line of code view,
> to %SubSt the
> information out.
>
> Are there any arguments one way or the other, besides
> readability? Speed?
> Data integrity?
>
> Thanks for your time,
> Capt.j
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L)
> mailing list
> To post a message email: RPG400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> or email: RPG400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.