[racket-dev] [racket] Long compilation+launch times

Would it make sense to detect when you CAN write into the main collects to make this feature more useful for working on the core?

Sent from my iPhone

On Aug 24, 2010, at 8:46 AM, Robby Findler <robby at eecs.northwestern.edu> wrote:

> I've just pushed a change to drracket so that it now will compile
> files in the collection paths, but not in the main collection path
> where the distribution is (as that is the one where thigns should be
> compiled already and also the one where you might not have write
> access). It also still avoids compiling in the planet cache (but still
> compiles in devel links).
> 
> Do let me know if you (or anyone!) run into any problems wrt compilation.
> 
> Thanks
> Robby
> 
> On Wed, Aug 4, 2010 at 9:10 AM, Laurent <laurent.orseau at gmail.com> wrote:
>> 
>> 
>> On Wed, Aug 4, 2010 at 15:12, Robby Findler <robby at eecs.northwestern.edu>
>> wrote:
>>> 
>>> Oh, that explains it. When it is in a collection, then drracket's
>>> auto-compile feature disables itself, since collections are not
>>> generally assumed to be writeable (as they are, roughly speaking the
>>> "standard libraries" and could be in some shared place).
>> 
>> That makes sense, thank you!
>> 
>>> You can work around this by explicitly calling mzc periodically from a
>>> shell (but you must be sure to call it if you change exported
>>> identifiers (or anytime you get a strange error)).
>> 
>> My collection is in ..../Scheme-svn/
>> running mzc inside ..../Scheme-svn/common works perfectly, but
>> inside ..../Scheme-svn/gui-tools it doesn't because in these files there
>> are:
>> (require common/something)
>> 
>> and mzc fails with the "collection not found" error.
>> Do I need to change my requires to relative paths, or should I had the
>> collection path to mzc (and then, how?) ?
>> 
>> Or even better: is there a way to add a collection permanently
>> (such as in the preferences), so that I don't have to declare them each
>> time I run racket, gracket, mzc, etc.
>> 
>> 
> _________________________________________________
>  For list-related administrative tasks:
>  http://lists.racket-lang.org/listinfo/dev