The site seems up. We had a regression that made it very unreliable,
crashing every few hours. It should be back to crashing every couple months
now.
If you want to read the docs offline, you can do this (takes several
minutes to run, Factor will hang in the meantime):
USE: help.html generate-hel
The site is up for me. I hit docs, planet, and main site (factorcode.org)
without an issue.
On Wed, Mar 19, 2014 at 12:02 AM, Dave Carlton
wrote:
> Still down here :(
>
> I can mirror the site once you get it up.
>
> On Mar 11, 2014, at 21:01 , John Benediktsson wrote:
>
> It looks like we migh
Still down here :(
I can mirror the site once you get it up.
On Mar 11, 2014, at 21:01 , John Benediktsson wrote:
> It looks like we might have tracked down the issue. I have updated
> factorcode.org and will see if it stays running now.
>
> Best,
> John.
>
>
> On Tue, Mar 11, 2014 at 6:59
2014-03-18 14:12 GMT+01:00 Jon Harper :
> In this case, it's more complicated then a single with-destructor scope,
> because I use the destructors to call libyaml's destroy function on the
> struct, so that the same memory can be reused between the calls to libyaml
> for this struct. So I really ne
In this case, it's more complicated then a single with-destructor scope,
because I use the destructors to call libyaml's destroy function on the
struct, so that the same memory can be reused between the calls to libyaml
for this struct. So I really need to destroy it right away before the next
call
Hi Jon,
2014-03-17 21:57 GMT+01:00 Jon Harper :
> Hi list,
> I am working with libyaml, a C library to parse yaml docs. Some libyaml
> functions give string results by malloc'ing memory and giving back pointers
> to those strings in a struct. They then require the caller to call a libyaml
> "destr
