From the output side, it probably isn't hard, but there is no way succinct way to tell the compiler which classes should use @export or not. You could annotate the class definitions, but then you can't choose to output @export without changing source.
Why do you think we need per-class control over this output? -Alex On 8/7/17, 8:54 AM, "Harbs" <harbs.li...@gmail.com> wrote: >Cool. > >How difficult would it be to allow this on a class-by-class basis? > >> On Aug 7, 2017, at 6:35 PM, Alex Harui <aha...@adobe.com.INVALID> wrote: >> >> First thing I will do, though, is allow turning off @export output on >> entire compiler sessions. That might allow you to have your text engine >> and your application logic more aggressively renamed but not require us >>to >> fix code in other SWCs that might use bracket access. >
