Hi, all,
This time we're demonstrating two different repos using the exact same copy
of the CGI framework code, only different bootstrap CGI scripts (which tell
them which repo to use and their project's primary site URL, for creating
certain external links):
http://fossil.wanderinghorse.net/repo
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
6 matches
Mail list logo
