Re: [Loco-dev] concerning locod

[TOK]

On Mon, 2002-09-09 at 20:14, Janico Greifenberg wrote:

> > changes to loco.h
> > i added loco_get_local_ips (from address.c). i don't understand while
> > loco-msg does compile (without), but copy and paste brought this up.
> > shall i use this at all?
> 
> Don't use it, use loco_get_local_ifs () like in loco-msg.c. C does not require
> a function to be declared before using it, so the compiler does not complain.

ok, but this comes from loco-msg (function run):
ips = loco_get_local_ips (NULL);

> > created locod subdir with:
> > locod.h - types, errors and global var (pointer)
> > config_parser.c - so we don't need to specify key, bootstrap ... as
> > arguments. i think we will surely need something like this.
> > locod.conf - xml style
> > 
> > daemon.c - ripped of loco-msg.c (pretty much nothing here)
> > starter.c - get & use params, load config, start daemon.c::locod_run()
> 
> Please do not do this.
> I want to move eveything out of the loco module exept the library since 
> libtool
> does not work too well with executables. 

sorry to say so, but a already have done (see below)
> 
> > 
> > i will update to cvs sometime this night, short of any wonders this code
> > will NOT compile (thus not included in loco-make, try make in locod).
> > i do this, as i try to prevent the same code written twice and think are
> > and me (or anyone) needs some base to start from (or so to say: sorry
> > about broken code).
> 
> Code wich does not compile is not supposed to be in the CVS.

i am aware of this, but there was no code (on locod) there before. i
find it easier to develop something when there already is some code to
interact with and arne wasn't sure if could spare the time to do it. i
don't have the skills to work on the library, thus i do apps. i just saw
the need for something to act (somewhat) like locod will, so i wrote
some prototype.
> 
> I am sorry to have to discourage you, but I want to decide the basic structure
> of the project myself and I am not done yet. I am for example thinking about
> using Guile (Scheme) for Remote Procedure Calls and configuration in the
> daemon. 
> So please don't commit anything to
> the CVS yet, but send patches to this list and I will integrate them. I have
> never done anything like this before so I have to try out many things. Having
> other people try out things on their own does not help, so please stay away
> from the CVS for now.
> (This is meant for everybody).
> 
> Thanks for your patience
>        Divo

i am not that discouraged that easily *g*. i won't touch the cvs archive
from now on, though i think that it's not hard to (re)move files & dirs;
so what dirs to use if i want to work on something (with arne)?

to undo changes to loco.h you could "cvs -O 1.9" in loco/loco as
(currently) only loco.h is version 1.9, though the correct solution
seems to be "cvs update -j 1.9 -j 1.8 loco.h" (in loco/loco).

in case you hadn't noticed, i did update loco/data.c a few days before.
address@hidden:~/Programming/loco/loco$ cvs diff -r 1.6 -r 1.7 data.c 
Index: data.c
===================================================================
RCS file: /cvsroot/loco/loco/loco/data.c,v
retrieving revision 1.6
retrieving revision 1.7
diff -r1.6 -r1.7
294c294
<   memset (ctx->sax, sizeof (my_handler), 0);
---
>   memset (ctx->sax, 0, sizeof (my_handler));

i will send this kind of thing (should any further occur to me) as diff
to this list.

best regard, tok

ps: when it comes to code, i tend to forget the virtue of patience ;-)