Allow a DATASET definition to be assigned a row

Environment

N/A

Description

Hi,

I've been demoing the Tomita variant of PARSE to my colleagues, using the calculator example in the ECL ref manual. I notice that you can assign the result from MATCHROW to DATASET(<record structure>) if said item is in the result rec, but not if the left-hand side of the expression is a standalone local DATASET.

So what's the difference between

and

Yours

Allan

Conclusion

None

Activity

Show:

Gavin Halliday June 10, 2019 at 12:28 PM

The rationale is that DATASET(r) xxx := ...; is creating a definition, rather than an assignment.  I was going to close as won't fix, but it is not unreasonable to support it, and  I think the fix is trivial.  If it proves to have no consequences I will release the fix.

Gavin Halliday May 31, 2019 at 11:40 AM

Investigate and either fix or close

Allan Wrobel May 22, 2019 at 2:16 PM

THanks, Gavin that fixed it. It's just strange that one needs to do this. 

What's the underlying rationale, re ECL for having to explicitly state DATASET in this instance?

its managed to cast to assign to SELD.ds := without having to explicitly state DATASET.   

Yours

Allan

Gavin Halliday May 22, 2019 at 2:09 PM

I suspect you need
DATASET(attrRec) xxx := DATASET(MATCHROW(e0));

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Minor

Fix versions

Pull Request URL

Affects versions

Due date

Created May 17, 2019 at 9:01 AM
Updated July 10, 2019 at 12:05 PM
Resolved June 14, 2019 at 9:36 AM