[erlang-questions] Subtle behaviour of Erlang scheduler

Ulf Wiger (TN/EAB) <>
Fri May 25 16:45:07 CEST 2007


Actually, c() does load the new module.

>From c.erl in stdlib:

c(File, Opts0) when list(Opts0) ->
    Opts = [report_errors,report_warnings|Opts0],
    case compile:file(File, Opts) of
        {ok,Mod} ->                             %Listing file.
            machine_load(Mod, File, Opts);
        {ok,Mod,_Ws} ->                         %Warnings maybe turned
on.
            machine_load(Mod, File, Opts);
        Other ->                                %Errors go here
            Other
    end; 

BR,
Ulf W

> -----Original Message-----
> From:  
> [mailto:] On Behalf Of KatolaZ
> Sent: den 25 maj 2007 16:38
> To: Philip Robinson
> Cc: 
> Subject: Re: [erlang-questions] Subtle behaviour of Erlang scheduler
> 
> On Fri, May 25, 2007 at 09:53:49PM +1000, Philip Robinson wrote:
> > This might be a silly question, but after you compiled the code with
> > c() did you load the module again with l()?  If not, you 
> will still be 
> > running the older code in the shell.
> > 
> 
> yes, philip, we did. And the result does not change, unfortunately.
> 
> HND
> 
> Enzo
> 
> --
> [ Enzo Nicosia aka KatolaZ --- GLUG Catania -- Freaknet 
> Medialab ] [ me [at] katolaz.homeunix.net -- 
> http://katolaz.homeunix.net -- ] [ GNU/Linux User:#325780/ICQ 
> UIN: #258332181/GPG key ID 0B5F062F ] [ Fingerprint: 8E59 
> D6AA 445E FDB4 A153 3D5A 5F20 B3AE 0B5F 062F ] 
> _______________________________________________
> erlang-questions mailing list
> 
> http://www.erlang.org/mailman/listinfo/erlang-questions
> 




More information about the erlang-questions mailing list