<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div>Almost all process registrations should be local to the module that registers<br>them. I proposed<br><br> -pidname(<atom>).<br><br>for declaring a module-locale atomic variable to hold pids. This would be both<br>safer than the global registry and more efficient. The global registry would<br>remain for those things that genuinely need to be global.<br></div></blockquote></div><br><div>Presuming that the module name is , say, <font class="Apple-style-span" face="'Courier New'">test</font>, how is:</div><div><br></div><div><font class="Apple-style-span" face="'Courier New'">-pidname( test )</font></div><div><br></div><div>different from:</div><div><br></div><div><font class="Apple-style-span" face="'Courier New'">register( ?MODULE, self() )</font>?</div><div><br></div><div><div>Also, how would you run multiple instances of the same module within the same run-time?</div><div>Your proposal may appear to solve one problem (that is, if one chose to call it a problem), but appears to introduce at least one more.</div><div><br></div><div>V/</div><div><br></div><div><br></div></div></body></html>