testing codes in erl with running processes

Fri Apr 25 15:43:59 CEST 2003

>>     I just realized that in my process, I refer to an ets table.
>>     And an ets table is associated with the running shell.
>>     This should explain why that process dies.
>>     If this is the case, I probably have no way to avoid this from
>>     happening.  The easy way is to develop code in another erl ?
>write a function that spawns a process, and let that process:
>1 create the ets table
>2 not die

  Yes, the problem is resolved. 
  Now, the ets table is owned by the process instead of the shell.
  Thanks for reminding me of the scoping!

More information about the erlang-questions mailing list