[erlang-questions] ANNOUNCEMENT: Chronos 0.0.1 timer utility

[Torben Hoffmann]

Hi,

I have provided a bit more information and bumped the version to v0.0.2.

Instructions for how to use Chronos with rebar is now given.

Cheers,
Torben

On 25/2/12 20:37 , Torben Hoffmann wrote:
>
>
> On 25/2/12 13:28 , Kirill Zaborsky wrote:
>> I think it can be seen in 
>> https://github.com/lehoff/chronos/commit/b9612ea73090f8037b47dc9b77045b3344df05cd 
>>
>> BTW I do not understand why rebar support was removed (I think it's 
>> not a problem to have a branch with rebar support for people who use it).
> Chronos wil build with rebar as it is right now - I tested that. Given 
> the lack of a rebar.config file it will not grab gproc, but there is a 
> reason for this.
>
> I took out the rebar.config since I doubt I will ever have a specific 
> version need for gproc, so instead of imposing a specific version or 
> just run with the latest I wanted to make it clear that the user has 
> to try things out and handle potential conflicting needs for gproc.
>
> I had all the good intentions of clearly explaining this, but as you 
> all know the road to hell is paved with good intentions...
>
> I will provide a pseudo .rel file and an INSTALL file so that it 
> becomes clear to people how to use Chronos.
>
> Cheers,
> Torben
>
>>
>> Kind regards,
>> Kirill Zaborsky
>>
>> 2012/2/25 Zabrane Mickael <zabrane3@REDACTED 
>> <mailto:zabrane3@REDACTED>>
>>
>>     Hi Torben,
>>
>>     It seems that *chronos* depends on *gproc*. Right?
>>
>>     Which version of *gproc* are you using as there are plenty of
>>     forks on github?
>>     https://github.com/uwiger/gproc/network
>>
>>     Nice work ...
>>
>>     N.B: IMHO, you should adapt the doc accordingly
>>
>>     Regards,
>>     Zabrane
>>
>>     On Feb 24, 2012, at 9:00 AM, Torben Hoffmann wrote:
>>
>>>     To whom it may concern.
>>>
>>>     I have released Chronos-0.0.1 at https://github.com/lehoff/chronos
>>>
>>>     Chronos is a small timer utility that can help deal with timers
>>>     without too much bookkeeping and suggest a design of components
>>>     that makes it easy to test the functionality of timers without
>>>     having to wait for them to expire.
>>>
>>>     There is also a short overview of the existing timer solutions
>>>     since you might have a problem that is better solved with
>>>     something else than Chronos.
>>>
>>>     Chronos comes with a QuickCheck test suite and an example of how
>>>     to abstract time from your tests.
>>>
>>>     Feedback is most welcome!
>>>
>>>     Cheers,
>>>     Torben
>>>
>>>     -- 
>>>     http://www.linkedin.com/in/torbenhoffmann
>>>
>>>     _______________________________________________
>>>     erlang-questions mailing list
>>>     erlang-questions@REDACTED <mailto:erlang-questions@REDACTED>
>>>     http://erlang.org/mailman/listinfo/erlang-questions
>>
>>
>>     _______________________________________________
>>     erlang-questions mailing list
>>     erlang-questions@REDACTED <mailto:erlang-questions@REDACTED>
>>     http://erlang.org/mailman/listinfo/erlang-questions
>>
>>
>
> -- 
> http://www.linkedin.com/in/torbenhoffmann

-- 
http://www.linkedin.com/in/torbenhoffmann

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20120225/b29ba241/attachment.htm>