emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Thierry Banel <tbanelwebmin@free.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Babel support for the D language
Date: Sun, 15 Dec 2013 14:35:10 -0700	[thread overview]
Message-ID: <8738lt3ibt.fsf@gmail.com> (raw)
In-Reply-To: loom.20131214T194616-410@post.gmane.org

Thierry Banel <tbanelwebmin@free.fr> writes:

> Eric Schulte <schulte.eric <at> gmail.com> writes:
>
>> 
>> I think this incorporation into ob-C.el would be the next logical step.
>> You'd want to use the `org-babel-c-variant' in the same manner as C++
>> does currently.  But there's no rush, and any changes there couldn't be
>> merged until after your FSF copyright assignment forms have been
>> completed.
>> 
>> Best Regards,
>> 
>
> Hi Eric
>
> Done. The merging of ob-C.el and ob-D.el is done.
> It is at the end of this file:
> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-D.html
> Actually, you are right, it makes sense to share common processing in a
> single *.el.
>
> I fixed what seems to be a bug.
> Tables were translated in C & C++ as something like:
>   char MyTable[7][2][11] = { ... };
> I changed that to:
>   const char* MyTable[7][2] = { ... };
> Because the former assumed that all content in the Org table were strings
> 11-1 characters long.
> Other than that, the behavior of C & C++ remains the same,
> and the code is very close to the original ob-C.el
>
> Also, in the future we may lift the constraint that tables have to be
> homogeneous
> (all ints, or all doubles, or all strings).
> But that's another story.
>
> 12 days have passed since I paper-mailed my copyright assignment to
> the FSF.  No news.  In the meantime, if you want to use my work, do
> so: it is copyrighted with the GPL 3 or later.
>

Yes, the FSF is occasionally very slow.

Perhaps someone with FSF connections can speed things up.  When you do
get the assignment back please let me know and send a patch of your
changes against the Org-mode repository (either to me directly or on
list, formatted with "git format-patch") and I'll apply it.

Thanks!

>
> Regards,
> Thierry
>
>
>

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D

      reply	other threads:[~2013-12-15 21:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 17:06 Babel support for the D language Thierry Banel
2013-11-28 17:51 ` Thomas S. Dye
2013-11-28 19:02   ` Thierry Banel
2013-11-28 20:57     ` Thomas S. Dye
2013-11-28 22:32     ` Nick Dokos
2013-11-29  7:40       ` Thierry Banel
2013-11-29 15:06         ` Nick Dokos
2013-11-29 20:19           ` Thierry Banel
2013-11-30  7:42   ` Thierry Banel
2013-11-30 17:56     ` Thomas S. Dye
2013-12-01 14:08       ` Thierry Banel
2013-12-01 14:13 ` Eric Schulte
2013-12-01 16:08   ` Thierry Banel
2013-12-01 18:04     ` Eric Schulte
2013-12-01 18:43       ` Thierry Banel
2013-12-14 18:49       ` Thierry Banel
2013-12-15 21:35         ` Eric Schulte [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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8738lt3ibt.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tbanelwebmin@free.fr \
    /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://git.savannah.gnu.org/cgit/emacs/org-mode.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).