Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

//#IMPORT(LEGACY|MODERN) to control import semantics.

Description

This is a feature added to help migrate old users from the legacy import semantics.

The special format comment:

//#IMPORT(LEGACY)

means that all following ECL will use the legacy import rules.

//#IMPORT(MODERN)

ensures that it uses the new rules.

The idea is that attributes can gradually be moved over from legacy to modern, but adding
//#IMPORT (MODERN)
to the head of the file, and then fixing any resulting compile issues. Once most attributes are switched over
//#IMPORT(LEGACY)
can be added to any remaining attributes, and the default for the system can be switched from legacy. Any remaining attributes can then be changed as required.

NOTE: Slightly unusually //#IMPORT within a macro definition only applies to the contents of that macro definition. This allows exported macro definitions to be switched over in the same way.

Conclusion

None

relates to

Activity

Show:

charles morton December 13, 2017 at 2:29 PM

W20171213-091611 - dataland example as requested

Gavin Halliday December 13, 2017 at 11:07 AM

It should be possible to add it to each attribute separately.  And the second example should have failed.  Do you have references to the workunits?  I would only expected it to have no effect on a system that doesn't support it (i.e. pre 6.2)

 

charles morton December 7, 2017 at 3:05 PM
Edited

this sounds very promising, but i'd like to ask for a little clarification on how to use this.

naively, i was hoping that  builder window like this (in dataland) would now execute in under 20 seconds, but it doesnt

   //#IMPORT (MODERN)

   1+1;

then, i also thought that a builder window like this might fail, because it has no imports, but it doesnt.

   //#IMPORT (MODERN)
   sizeof(linking_h.layout_header)

maybe i have this wrong and the //#IMPORT (MODERN) needs to be added to most of the individual ECL attributes in the repository for this to take effect?

David Bayliss November 29, 2016 at 1:39 PM

EXCELLENT!!!!!!! THNX

Richard Chapman November 29, 2016 at 11:36 AM

FYI

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

Details

Components

Assignee

Reporter

Priority

Compatibility

Minor

Fix versions

Labels

Pull Request URL

https://github.com/hpcc-systems/HPCC-Platform/pull/9366

Created November 15, 2016 at 9:32 PM
Updated April 9, 2019 at 1:18 PM
Resolved November 29, 2016 at 11:36 AM

Flag notifications