On Wed, Feb 26, 2014 at 7:19 PM, Ron Wilson wrote:
> headed off a scheme for implementing our own shared library mechanism by
> offering to embed a simple, low overhead scripting engine. though the
> language chosen was not my first choice (for implementing the embedding),
> it still worked out.
On Wed, Feb 26, 2014 at 12:25 PM, Stephan Beal wrote:
> It's basically a JS-like data model (derived initially, in fact, from the
> same JSON code which runs fossil's JSON API), but provides a facility for
> clients to plug their own types into it (in a type-safe way - you don't
> have to blindly
On Wed, Feb 26, 2014 at 6:13 PM, Ron Wilson wrote:
> I haven't had a chance to look at your scripting engine, but I would have
> thought that the scripting bindings would have been implemented with
> "primitives" written in C that map the scripting engine's data model to C's
> data model.
>
It's
On Wed, Feb 26, 2014 at 6:00 AM, Stephan Beal wrote:
> On Wed, Feb 26, 2014 at 6:29 AM, Doug Franklin > wrote:
>
>> So, I'm kinda late to the party, since I only started using Fossil a year
>> ago, or so. But, I'd like to throw out a suggestion: something like
>> doxygen or javadoc so that the
On Wed, Feb 26, 2014 at 6:29 AM, Doug Franklin
wrote:
> So, I'm kinda late to the party, since I only started using Fossil a year
> ago, or so. But, I'd like to throw out a suggestion: something like
> doxygen or javadoc so that the documentation and source are the same
> artifact. Knuth tried w
On 2014-02-25 12:32, Stephan Beal wrote:
i haven't thought that far ahead :/. My docs tend to grow pretty large,
and porting them after a certain size becomes painful.
So, I'm kinda late to the party, since I only started using Fossil a
year ago, or so. But, I'd like to throw out a suggestio
On Tue, Feb 25, 2014 at 5:59 PM, Chad Perrin wrote:
> Do you plan to move the stuff into a Fossil wiki, eventually?
>
i haven't thought that far ahead :/. My docs tend to grow pretty large, and
porting them after a certain size becomes painful.
> I find
>
Google Docs problematic enough that I
On Mon, Feb 24, 2014 at 10:04:33PM +0100, Stephan Beal wrote:
> On Mon, Feb 24, 2014 at 9:37 PM, Chad Perrin wrote:
>
> > Is there some reason this kind of thing shouldn't be maintained in a
> > Fossil wiki instead of Google docs?
> >
>
> Yeah, i see the irony in it, but Fossil's just not the to
On Mon, Feb 24, 2014 at 10:04:33PM +0100, Stephan Beal wrote:
> On Mon, Feb 24, 2014 at 9:37 PM, Chad Perrin wrote:
>
> Is there some reason this kind of thing shouldn't be maintained in
> a Fossil wiki instead of Google docs?
>
>
> Yeah, i see the irony in it, but Fossil's just not the
On Mon, Feb 24, 2014 at 9:37 PM, Chad Perrin wrote:
> Is there some reason this kind of thing shouldn't be maintained in a
> Fossil wiki instead of Google docs?
>
Yeah, i see the irony in it, but Fossil's just not the tool for what i want
in this case: simplicity and real-time collaboration[1].
On Tue, Feb 18, 2014 at 08:55:51PM +0100, Stephan Beal wrote:
> Hi, all,
>
> FYI: the experimental libfossil script bindings have grown somewhat larger
> than originally anticipated, and i've started documenting them in a public
> Google Doc:
Is there some reason this kind of thing shouldn't be m
Hi, all,
FYI: the experimental libfossil script bindings have grown somewhat larger
than originally anticipated, and i've started documenting them in a public
Google Doc:
https://docs.google.com/document/d/1YsVMBNJfuZC7tIxqhNgK21O7dQyV0mnsfQRn0GMpU5I/view
(A few of you have been given write acce
12 matches
Mail list logo
