× 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: Another V5R1 query... Qualified DSs
  • From: "Peter Dow" <pcdow@xxxxxxxxx>
  • Date: Thu, 10 May 2001 12:47:24 -0700

Hi Barbara,

Instead of %allfieldsnamed(xxx), how about MOVEC or EVALC? Equivalent to
COBOL's MOVE CORRESPONDING? I won't hold my breath on those either...

When you say it's impossible to have name collisions with LIKEDS, are you
implying that with PREFIX it's possible to have name collisions that are
undetected by the compiler? I would think that

    d someds     ds
    d  fld1           1a
    d  fld2           1a

    d someds     ds       likeds(someds)

would certainly cause some name collisions, but they would be detected by
the compiler, as would

    d extds    e ds       extname(abc) prefix(a)

    d extds1   e ds       extname(abc) prefix(a)

In either case, someone goofed and the compiler would no doubt complain. Or
were you thinking of something else?

Regards,
Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax


> As I see it, there are 3 major benefits to this new feature.  The
> first is related strictly to QUALIFIED; most of the good stuff
> comes from LIKEDS.
> 1. Using QUALIFIED, you can code "type definition" data structures
>    in /COPY files without having to worry about subfield name
>    collision.
> 2. LIKEDS allows you to use data structure parameters in
>    prototyped procedures.
> 3. LIKEDS allows you to write your DS once and use the layout
>    for as many variables as you want.  (Formerly available only
>    with externally-described DS and PREFIX, and anyway, LIKEDS
>    is better than PREFIX because it's impossible to have name
>    collisions.)
>
> Regarding your wish to have all xxx subfields updated with a
> single assignment to xxx, I guess that might be cool, but I
> doubt it would have a very broad application.  For sure such
> a feature wouldn't be discussed using the term "qualified names".
> We didn't invent this term for RPG - many languages have qualified
> names, and it always means the same thing.
>
> How about %allfieldsnamed(xxx) = value.  (don't hold your breath :)


> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.