All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
	Thiago Farina <tfransosi@gmail.com>,
	git@vger.kernel.org, dag@cray.com,
	Nicolas Sebrecht <nicolas.s.dev@gmx.fr>,
	greened@obbligato.org
Subject: Re: libgit2 status
Date: Sat, 20 Oct 2012 09:58:17 +0200	[thread overview]
Message-ID: <50825999.5080208@op5.se> (raw)
In-Reply-To: <7vvce6i5j2.fsf@alter.siamese.dyndns.org>

On 10/19/2012 10:13 PM, Junio C Hamano wrote:
> Ramkumar Ramachandra <artagnon@gmail.com> writes:
> 
>> Thiago Farina wrote:
>>> [...]
>>> With some structure like:
>>>
>>> include/git.h
>>> src/git.c
>>>
>>> ...
>>>
>>> whatever.
>>> [...]
>>
>> Junio- is it reasonable to expect the directory-restructuring by 2.0?
> 
> I actually hate "include/git.h vs src/git.c"; you have distinction
> between .c and .h already.
> 

Agreed. The way libgit2 does it is to have "src/tag.[ch]", which are
for internal use, and then "src/include/tag.h" which is the published
version that others can use to write code against the tag library.
src/tag.h always includes src/include/tag.h, so no code needs to be
duplicated, but internal parts of the library can still use lower-
level stuff if it wants to. It's a good compromise when creating a
library from application code and there were no opaque types from
the start.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

      parent reply	other threads:[~2012-10-20  7:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 14:02 libgit2 status greened
2012-08-25  9:56 ` Andreas Ericsson
2012-08-25 20:46   ` Vicent Marti
2012-08-25 21:46     ` Nicolas Sebrecht
2012-08-25 22:32       ` Carlos Martín Nieto
2012-08-26  7:26       ` Elia Pinto
2012-08-26 18:28   ` Junio C Hamano
2012-08-26 18:56     ` Junio C Hamano
2012-08-27 16:13     ` dag
2012-08-27 17:10       ` Junio C Hamano
2012-08-27 18:49         ` dag
2012-08-27 19:44           ` Junio C Hamano
2012-08-27 21:21             ` dag
2012-08-27 21:40             ` Nicolas Sebrecht
2012-08-28 17:59               ` dag
2012-08-28 18:36                 ` Junio C Hamano
2012-10-19  0:42                   ` Thiago Farina
2012-10-19  3:54                     ` Ramkumar Ramachandra
2012-10-19 20:13                       ` Junio C Hamano
2012-10-19 22:11                         ` dag
2012-10-19 22:43                         ` Junio C Hamano
2012-10-20  1:21                         ` Thiago Farina
2012-10-20  7:58                         ` Andreas Ericsson [this message]

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=50825999.5080208@op5.se \
    --to=ae@op5.se \
    --cc=artagnon@gmail.com \
    --cc=dag@cray.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=greened@obbligato.org \
    --cc=nicolas.s.dev@gmx.fr \
    --cc=tfransosi@gmail.com \
    /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.