You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a fan of using multiple packages for larger languages or languages that embed other languages (such as SAS + SQL + SAS macro language). However maybe those different packages could be translated into multiple single-package languages in Lionweb, and even in Kolasu we could have each Language correspond to a single package.
I'm a fan of using multiple packages for larger languages or languages that embed other languages
Then we will find a way to support them
However maybe those different packages could be translated into multiple single-package languages in Lionweb, and even in Kolasu we could have each Language correspond to a single package.
Yes, I think this is one option. Probably it would be the most straightforward, however I think for that to work we should ensure we do not have circular dependencies among the packages.
If circular dependencies are needed and we cannot support with the approach you suggest, as an alternative approach we could translate them as a single language in LionWeb but add annotations indicating to which package they belong. Then we could use that information when generating code.
We should also consider exporting to LionWeb
The text was updated successfully, but these errors were encountered: