erlang spawn进程错误?

时间:2013-02-14 17:26:17

标签: process erlang spawn

我正在关注this tutorial,我尝试编译event.erl并根据

运行它
6> c(event).
{ok,event}
7> rr(event, state).
[state]
8> spawn(event, loop, [#state{server=self(), name="test", to_go=5}]).
<0.60.0>
9> flush().
ok
10> flush().
Shell got {done,"test"}
ok
11> Pid = spawn(event, loop, [#state{server=self(), name="test", to_go=500}]).
<0.64.0>
12> ReplyRef = make_ref().
#Ref<0.0.0.210>
13> Pid ! {self(), ReplyRef, cancel}.
{<0.50.0>,#Ref<0.0.0.210>,cancel}
14> flush().
Shell got {#Ref<0.0.0.210>,ok}
ok

但我似乎无法通过第8步,因为我得到了这个错误。

7> spawn(event, loop, [#state{server=self(), name="test", to_go=5}]).

=ERROR REPORT==== 14-Feb-2013::11:14:38 ===
Error in process <0.51.0> with exit value: {function_clause,[{event,loop,[{state,<0.32.0>,"test",5}],[{file,"event.erl"},{line,35}]}]}

<0.51.0>

以下是event.erl

-module(event).
-export([start/2, start_link/2, cancel/1]).
-export([init/3, loop/1]).
-record(state, {server,
                name="",
                to_go=0}).

%%% Public interface
start(EventName, DateTime) ->
    spawn(?MODULE, init, [self(), EventName, DateTime]).

start_link(EventName, DateTime) ->
    spawn_link(?MODULE, init, [self(), EventName, DateTime]).

cancel(Pid) ->
    %% Monitor in case the process is already dead
    Ref = erlang:monitor(process, Pid),
    Pid ! {self(), Ref, cancel},
    receive
        {Ref, ok} ->
            erlang:demonitor(Ref, [flush]),
            ok;
        {'DOWN', Ref, process, Pid, _Reason} ->
            ok
    end.

%%% Event's innards
init(Server, EventName, DateTime) ->
    loop(#state{server=Server,
                name=EventName,
                to_go=time_to_go(DateTime)}).

%% Loop uses a list for times in order to go around the ~49 days limit
%% on timeouts.
loop(S = #state{server=Server, to_go=[T|Next]}) ->
    receive
        {Server, Ref, cancel} ->
            Server ! {Ref, ok}
    after T*1000 ->
        if Next =:= [] ->
            Server ! {done, S#state.name};
           Next =/= [] ->
            loop(S#state{to_go=Next})
        end
    end.

%%% private functions
time_to_go(TimeOut={{_,_,_}, {_,_,_}}) ->
    Now = calendar:local_time(),
    ToGo = calendar:datetime_to_gregorian_seconds(TimeOut) -
           calendar:datetime_to_gregorian_seconds(Now),
    Secs = if ToGo > 0  -> ToGo;
              ToGo =< 0 -> 0
           end,
    normalize(Secs).

%% Because Erlang is limited to about 49 days (49*24*60*60*1000) in
%% milliseconds, the following function is used
normalize(N) ->
    Limit = 49*24*60*60,
    [N rem Limit | lists:duplicate(N div Limit, Limit)].

编辑:我试图通过添加来自此

的参数来更改函数循环
loop(S = #state{server=Server, to_go=[T|Next]}) ->

to this 

loop(S = #state{server=Server,name=EventName, to_go=[T|Next]}) ->

它仍然可以编译,但它不起作用,同样的错误......我想也许元组不匹配。然后它只演变为参数to_go=[T|Next]}不正确。

3 个答案:

答案 0 :(得分:2)

我认为问题在于你的loop / 1子句解包#state参数,使得to_go与列表进行模式匹配(即to_go = [T | Next])。但是,传入5(to_go = 5)将无法匹配[T |因此,循环/ 1将不匹配,您将没有匹配

的函数子句
loop(#state{server=self(), name="test", to_go=5})

答案 1 :(得分:2)

Erlang process event error中的问题相同。 start/2start_link/2time_to_go/1函数需要{{Year,Month,Day},{Hour,Minute,Second}}形式的时间参数,这就是当您使用5调用它们时失败的原因。 loop/1函数要求to_go的{​​{1}}字段为整数的列表,它将其解释为秒,并通过执行{等待总时间每个人{1}}。此服务器的目标是能够比Erlang在#state{}中直接等待更长的时间。

receive...after函数计算从现在到作为参数输入的日期/时间之间的秒数,然后将其分解为秒数列表,其中没有任何值大于最大值receive...after可以处理。

答案 2 :(得分:1)

这个表达式:

8> spawn(event, loop, [#state{server=self(), name="test", to_go=5}]).

适用于早期版本的代码,因为它是在整个教程中开发的。如果我正确阅读,这应该是正确的电话:

19> event:start("Event", 0).