Language design: multiple languages vs. pluggable scope dialects
Pluggable superlanguage version is much more flexible; would offer many benefits:
“Match this pattern over this EMF model, plus this DOORS/etc model, plus this traceability table between them” → easy with hybrid scopes
“Template patterns”, restrict certain patterns (both in the incremental and the stateless case) to a few user-supplied starting points (objects or identifiers) at runtime → this can be a use case for a user-supplied (unary) table
Pluggable superlanguage may take more initial effort
Runtime-level plus language-level composition
Solve editor content assist etc. issues…
import <<IVQLImportable on classpath>> <<details>>
Example importables: epackage, java, user-table etc. ← list should be extensible; also probably deprecate / remove the default case
“Details” could be Java package name, EPackage nsURI, user table name/class etc.
Give +1000% time budget to Zoltán :)
Timeframe? Is it meaningful to release 2.0 with language issues postponed?
