From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: unchanged functions between ccid-3 and ccid-4
Date: Tue, 25 Sep 2007 08:52:57 +0000 [thread overview]
Message-ID: <200709250952.57753@strip-the-willow> (raw)
In-Reply-To: <5bc4c4570709201928l270b24cdod359349ca3d3508@mail.gmail.com>
| > Anyway, I'm already identifying the candidate codes to be shared
| > between ccid3 and ccid4 if you didn't this yet. Another option is wait
| > for gerrit suggestion on this issue and discuss more about that and
| > define a strategy to avoid code repetition.
|
| See? Wait for Gerrit, wait for Arnaldo, reach a consensus on code layout
| first... nah, get something that works, when and if people send
| suggestions you react, but don't get lack of feedback on these matters
| to make you stop coding.
|
I'll say the same - the repository is yours, just keep working on it until
you have soomething that works for you - when there are actual problems with
the CCID3 code, please however mail them to the list.
I just remembered a very crude, but technically correct hack: if you want
to avoid the work of linking, header dependencies, one can include entire
source files using the preprocessor macro, e.g. in ccid4.c:
#include "ccid3.c" /* works as expected, all code is imported */
This allows small and clear code (only the `diff' needs to be added, but I think
the mainline guys don't like it so much :)
next prev parent reply other threads:[~2007-09-25 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 2:28 unchanged functions between ccid-3 and ccid-4
2007-09-21 10:00 ` Arnaldo Carvalho de Melo
2007-09-21 13:20 `
2007-09-25 8:52 ` Gerrit Renker [this message]
2007-09-26 13:22 ` Tommi Saviranta
2007-09-26 13:33 `
2007-09-26 13:45 ` Tommi Saviranta
2007-09-26 13:51 `
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200709250952.57753@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--cc=dccp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.