RE: Sorting a user space -- RPG400-L

Why 2047? I could make the PtrAry as large as I would like I think. And
if I ran out of room, I could use a file instead of the table - although
it would be slower.

Actually, I'm wrong. If your array had a name (which it doesn't) thenit'd be limited to 65535 bytes, and since each element is 32 bytes longyou'd have a 2047 limit.

But, since it's unnamed, it doesn't have that restriction. My mistake, Ilooked at it too quickly.

And the filler is necessary - at least on the compiler I use. It
complains about alignment otherwise.

Are you sure? I tried it with a V4R4, V5R1, V5R2 and V5R3 compiler, and Idid not have any problems.

(Plus, it doesn't make sense, since the filler has nothing to do with howthe field is aligned, the OVERLAY controls that)

I think you're right about the Align verb though - it's just hanging
there.

I tested it without that keyword on V4R4 and later as well, and thekeyword had no effect.

And the point was the idea - not necessarily my demonstration of perfect
syntax - I just typed this off the top of my head - after a glance at
some other code. In this case - it's the idea of using pointers to the
data in the user space as data itself that can be manipulated as any
other data can be.

It's a good idea, and is probably the best solution if you need to be ableto sort a list where the entries can all have different lengths. I wasjust pointing out some things about the technique, since many people whoread this list will see the ALIGN keyword, and the Filler field andthey'll think that they're required. Since this stuff is posted publiclyand available to every search engine, it makes sense to point these thingsout so that people aren't misled.


Please don't take it personally.