[erlang-questions] Confusing about gproc with global properties

[Ulf Wiger]

Hmpf! Thanks. Corrected, and some eunit tests added for good measure. :)

v0.2.1 pushed.

BR,
Ulf

On 18 Apr 2011, at 18:17, Gregory Haskins wrote:

> On 4/18/11 12:01 PM, Ulf Wiger wrote:
>> Hi Greg,
>> 
>> Thanks for noticing. I was about to push a new version anyway, so I
>> fixed that issue as well.
> 
> Cool, thanks!
> 
>> 
>> Try the latest version: https://github.com/esl/gproc/tree/v0.2.0
>> 
> 
> I confirmed that it does appear to now use [g,l] by default.  Note I am
> also seeing this issue:
> 
> (gproctest@REDACTED)3> gproc:reg({p, g, foo}, bar).
> true
> (gproctest@REDACTED)4> gproc:reg({p, l, foo}, bar).
> true
> (gproctest@REDACTED)5> qlc:e(qlc:q([P || P <- gproc:table(props)])).
> ** exception error: no function clause matching gproc:type({'_',p})
>     in function  gproc:pattern/2
>     in call from gproc:select/3
>     in call from gproc:'-table/2-fun-2-'/3
>     in call from qlc:collect/1
>     in call from qlc:eval/2
> (gproctest@REDACTED)6> qlc:e(qlc:q([P || P <- gproc:table({all, props})])).
> ** exception error: no function clause matching gproc:type({'_',p})
>     in function  gproc:pattern/2
>     in call from gproc:select/3
>     in call from gproc:'-table/2-fun-2-'/3
>     in call from qlc:collect/1
>     in call from qlc:eval/2
> 
> Could be "pilot error", too ;)  Am I doing something unsupported?
> 
> -Greg
> 

Ulf Wiger, CTO, Erlang Solutions, Ltd.
http://erlang-solutions.com