The compiler internals could be coded to use binary names. Obviously, generators would do something sensible.
For example, I know that rebind rules in gwt.xml are tracked by source name. Well, those could get looked up in TypeOracle and translated to the appropriate binary name and tracked that way. You would always to one-way conversions from source->binary and never back. On Fri, May 27, 2011 at 1:01 PM, John Tamplin <[email protected]> wrote: > On Fri, May 27, 2011 at 12:53 PM, Scott Blum <[email protected]> wrote: > >> On Fri, May 27, 2011 at 10:12 AM, John Tamplin <[email protected]> wrote: >> >>> I don't think that solves the problem -- let's say we store Foo/Bar$Baz >>> internally and convert it to a source name where needed. How do we know >>> whether the class name is Bar$Baz or Baz inside of Bar? The problem is >>> simply if you allow $ in a class name, binary and internal names are lossy >>> too as they no longer encode the difference. >>> >> >> My point is to NOT convert it to source names, do everything in binary. >> > > So when you generate source code, how do you do that? Or let's just say > you want to get the simple class name -- in the example, is it Bar$Baz or > Baz? The point is you don't have the information necessary to tell. > > -- > John A. Tamplin > Software Engineer (GWT), Google > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
