From: Petr Baudis <pasky@suse.cz>
To: Dmitry Potapov <dpotapov@gmail.com>
Cc: cte <cestreich@gmail.com>, git@vger.kernel.org
Subject: Re: linking libgit.a in C++ projects
Date: Thu, 31 Jul 2008 13:14:46 +0200 [thread overview]
Message-ID: <20080731111446.GO32184@machine.or.cz> (raw)
In-Reply-To: <20080731105727.GF7008@dpotapov.dyndns.org>
On Thu, Jul 31, 2008 at 02:57:27PM +0400, Dmitry Potapov wrote:
> On Thu, Jul 31, 2008 at 02:53:37AM -0700, cte wrote:
> > I'm writing a git gui for OS X using cocoa/Objective-C++, and rather
> > than being lame and parsing the output the various git commands, I'm
> > using libgit.a to provide all of the needed functionality for my app.
>
> Don't do that! libgit.a is an internal library used solely to build
> git binaries. It means that its interface can be cahnged at any time.
I don't think this is that big a problem; there are applications that
are doing this already, e.g. cgit, and if you tie your application to
a particular git version by for example making git a submodule of your
source, this is pretty safe; it will just mean that you will have to
do some non-trivial porting of your code to the new interface each time
you update - but I think large changes in the interface are pretty rare
in practice by now, and there shouldn't be much on the horizon either(?).
> > However, the git source uses a few reserved C++ keywords; namely
> > 'typename', and 'new'.
>
> Because this source code are meant to be compiled by C and not by C++!
> Even if we will have real git library for other applications to use,
> it still be compiled only by C. Thus, C++ keywords are not issue.
What would be the reason to disallow C++ users? The costs aren't that
high, and (modulo, say, extern "C" { }) there should be no C-C++
compatibility issues, right?
--
Petr "Pasky" Baudis
As in certain cults it is possible to kill a process if you know
its true name. -- Ken Thompson and Dennis M. Ritchie
next prev parent reply other threads:[~2008-07-31 11:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 9:53 linking libgit.a in C++ projects cte
2008-07-31 10:57 ` Dmitry Potapov
2008-07-31 11:10 ` cte
2008-07-31 11:16 ` Pedro Melo
2008-07-31 11:20 ` Petr Baudis
2008-07-31 11:20 ` cte
2008-07-31 18:27 ` Sverre Rabbelier
2008-07-31 21:44 ` cte
2008-07-31 21:51 ` Sverre Rabbelier
2008-07-31 21:58 ` Shawn O. Pearce
2008-07-31 22:10 ` Sverre Rabbelier
2008-08-04 14:52 ` Steve Frécinaux
2008-08-01 1:17 ` cte
2008-08-01 1:54 ` Linus Torvalds
2008-08-01 2:12 ` cte
2008-07-31 22:23 ` Dmitry Potapov
2008-07-31 11:14 ` Petr Baudis [this message]
2008-07-31 11:18 ` cte
2008-07-31 12:34 ` Dmitry Potapov
2008-07-31 13:04 ` Boaz Harrosh
2008-07-31 14:44 ` Dmitry Potapov
2008-07-31 18:37 ` Alex Riesen
2008-07-31 18:55 ` Avery Pennarun
2008-08-03 20:12 ` Alex Riesen
2008-08-04 8:57 ` Boaz Harrosh
2008-07-31 21:31 ` cte
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080731111446.GO32184@machine.or.cz \
--to=pasky@suse.cz \
--cc=cestreich@gmail.com \
--cc=dpotapov@gmail.com \
--cc=git@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).