On Thu, Feb 11, 2010 at 5:33 PM, Lex Spoon <[email protected]> wrote: > >> Besides, what is gained by having the user have to arrange this copying >> themselves rather than the current method of sending it as part of the >> compile process? For example, distributed C/C++ compilers send the >> preprocessed source to the worker nodes, so they don't have to have the >> source or the same include files, we currently send the AST which is a >> representation of the source, etc. >> > > Compared to the status quo, we gain much faster builds. > > Compared to automatically copying, we have a fully specced out proposal. > :) If we try to automatically copy dependencies, how would we we know > exactly what to copy? >
That is exactly my point -- the C++ example sends the preprocessed source to the worker nodes, so they don't have to have the dependencies or the right include path or whatever. The analogy here would be for GWT to send all of the collected source, either in its native form or as is currently done in a parsed AST form, to the worker nodes. -- John A. Tamplin Software Engineer (GWT), Google -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
