This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Merger of the "dmalcolm/jit" branch
- From: Jeff Law <law at redhat dot com>
- To: David Malcolm <dmalcolm at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Cc: jit at gcc dot gnu dot org
- Date: Mon, 13 Oct 2014 15:15:53 -0600
- Subject: Re: [PATCH] Merger of the "dmalcolm/jit" branch
- Authentication-results: sourceware.org; auth=none
- References: <1411497912 dot 16438 dot 27 dot camel at surprise>
On 09/23/14 12:45, David Malcolm wrote:
As mentioned before, I'm using Sphinx for documentation (and also
checking in autogenerated .texinfo for those who want docs without a
sphinx toolchain installed).
I'm interested in how Sphinx is working for this project as well as the
Ada folks who have started using it -- with an eye towards Sphinx
instead of texi as the canonical source format for GCC's documentation.
I realize nobody's agreed to that, but just to be clear, that's where
I'm hoping things will go.
The API docs currently have this caveat:
"Note that libgccjit is currently of "Alpha" quality; the APIs
are not yet set in stone, and they shouldnât be used in
production yet."
Do I need to declare a frozen API before this can go in, or is it
acceptable to carry this within the tree as an "experimental" feature?
I don't think you need to freeze an API at this stage -- it can be noted
as experimental and that folks should expect API changes over time and
that they will need to compensate for it in their code.
Jeff