I imagine if I was using the framework in a more orthodox way, I'd
probably get that error too. I'm trying to use erlydb outside of
erlyweb proper to implement a couple of gen_servers. I was probably
masking the problem by calling code:unstick_dir("./ebin") but I can't
see any other way around the problem since erlydb wants to modify the
modules at runtime.
I'm thinking about tweaking erlydb to be more compile-time friendly
and save the generated modules to files. I know the guts to support
this already exist but it looks like they just need to be tied
together and surfaced in a friendly way.
--Kevin
On Dec 28, 2007, at 2:25 PM, Bryan Fink wrote:
>
> Hmm...when I ran into this problem, a warning message *was* emitted
> when erlyweb tried to load user.erl. The warning mentions that "user"
> is a "sticky directory."
>
> It will happen with other modules as well:
> http://osdir.com/ml/lang.erlang.general/2002-10/msg00100.html
>
> Maybe the warning should be a little louder, but it seems like the
> hook is there already.
>
> -Bryan
>
> On Dec 28, 12:46 pm, "Yariv Sadan" <[EMAIL PROTECTED]> wrote:
>> Yes, definitely. I think ErlyDB should just crash when it tries to
>> compile a module called 'user' because a few people have ran into
>> this.
>>
>> On Dec 28, 2007 8:34 AM, Kevin A. Smith <[EMAIL PROTECTED]>
>> wrote:
>>> I was thinking about cooking up a patch to emit a warning message
>>> when
>>> erlydb tries to process a builtin class like this one. Would this be
>>> useful to anyone else?
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"erlyweb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
