On Fri, Jul 18, 2014 at 3:27 PM, Stephan Beal wrote:
> The core API bits have all been ported to s2. Sample scripts/unit tests:
>
> http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/dir/s2/unit2
>
> There's some utility-level code left to port (filesystem utils and such)
>
Done - only t
On Thu, Jul 17, 2014 at 8:38 PM, Stephan Beal wrote:
> Unless i get called off of vacation back to work next week, i "should"
> have the remaining bits ported from the older binding by this time next
> week.
>
The core API bits have all been ported to s2. Sample scripts/unit tests:
http://fossi
On Thu, Jul 17, 2014 at 10:37 PM, Andy Goth wrote:
> http://wiki.tcl.tk/3840
Interestingly, when i dlclose() modules, valgrind shows dlclose() (or
lt_dlclose()) as leaking memory. It's not safe, generically speaking, to
close DLLs, anyway, because simply opening them might have side effects
whi
On Thu, Jul 17, 2014 at 10:37 PM, Andy Goth wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 7/17/2014 3:22 PM, Stephan Beal wrote:
> > in terms of memory use, it seems to be on par with lua, and lua is
> > the lightest-memory interpreter i've yet run through valgrind. Most
> > of
On 7/17/14, Andy Goth wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 7/17/2014 3:22 PM, Stephan Beal wrote:
>> in terms of memory use, it seems to be on par with lua, and lua is
>> the lightest-memory interpreter i've yet run through valgrind. Most
>> of them individually leak mor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/17/2014 3:22 PM, Stephan Beal wrote:
> in terms of memory use, it seems to be on par with lua, and lua is
> the lightest-memory interpreter i've yet run through valgrind. Most
> of them individually leak more memory than lua and s2 allocate
> comb
On Thu, Jul 17, 2014 at 10:06 PM, Ron W wrote:
> Very interesting project. Somehow, I missed that th1ish wasn't a modified
> TH1 engine. While I appreciate a C-like syntax, I am a bit surprised to see
> the switch away from TCL-like syntax.
>
i kept some of it, but some of it partly conflicts wi
Very interesting project. Somehow, I missed that th1ish wasn't a modified
TH1 engine. While I appreciate a C-like syntax, I am a bit surprised to see
the switch away from TCL-like syntax.
Will be interesting to see how this project compares to other ;scripting
engines designed for embedding, like,
I keep hoping to make time to work on a Chicken Scheme binding for
libfossil (it would be really help in several projects I'm working on) so
I'm keenly following your progress on libfossil. Anyhow in your post I
couldn't help but think of Greenspuns Tenth Rule of Programming :)
http://c2.com/cgi/w
Hi, all,
the past two months have seen a complete rewrite of my own personal toy
scripting engine, largely inspired by limitations uncovered in it while
binding libfossil to it. As of today, partial libfossil bindings are in
place for the new language (the db abstraction layer is done), and there'
10 matches
Mail list logo
