From: Ernesto Durante <stobossey@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: babel: ob-C with Visual C++ and compilation-mode
Date: Fri, 15 Aug 2014 19:22:02 +0200 [thread overview]
Message-ID: <87lhqp7jnp.fsf@gmail.com> (raw)
In-Reply-To: <53ED1EB0.3030500@free.fr> (Thierry Banel's message of "Thu, 14 Aug 2014 22:40:16 +0200")
> Well... In this example, we go down from 9 lines to 7 lines. Ok fair.
> But the price is a new syntax to learn:
> ////main////
> Is it wise to add an org-mode specific syntax to C++ (which already has
> a lot) ?
>
> Being noisy is a weakness of C++.
> I think it is not the responsibility of org-mode to fix that.
>
> Now, org-mode is already able to process main()-less blocks in simple cases.
>
> #+BEGIN_SRC C++
> printf("hello\n");
> #+END_SRC
>
> If we can find a way to extend this feature to more cases,
> without needing a long documentation,
> then, sure, it would be a nice improvement.
I agree with you. Creating a new syntax is not a good idea.
However, in some way, ob-C has created a new syntax implicitly by
instantiating a new main in absence of such a function in the source
block.
So why not to extend this idea by allowing a user defined function to
parse the source block. The default function is clearly
org-babel-C-ensure-main-wrap.
We could create a new header :wrap which replaces :main and holds the user
defined function. It can take three values
nil, org-babel-C-ensure-main-wrap(default), or user-defined-function.
So, in this way user-defined-function holds my own syntax for my future presentation.
What do you think ?
Best
Ernesto
next prev parent reply other threads:[~2014-08-15 17:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 16:16 babel: ob-C with Visual C++ and compilation-mode Ernesto Durante
2014-08-11 19:40 ` Thierry Banel
2014-08-12 14:24 ` Ernesto Durante
2014-08-12 22:03 ` Thierry Banel
2014-08-13 20:58 ` Ernesto Durante
2014-08-14 20:40 ` Thierry Banel
2014-08-15 17:22 ` Ernesto Durante [this message]
2014-08-17 11:20 ` Thierry Banel
2014-08-18 11:19 ` Ernesto Durante
2014-08-18 12:51 ` Eric Schulte
2014-08-24 13:05 ` Ernesto Durante
2014-08-28 14:02 ` Eric Schulte
2014-08-18 19:59 ` Thierry Banel
2014-08-20 20:40 ` Ernesto Durante
2014-08-21 19:48 ` Thierry Banel
2014-08-24 12:57 ` Ernesto Durante
2014-08-28 19:44 ` Thierry Banel
2014-08-18 2:41 ` Eric Schulte
2014-08-18 2:40 ` Eric Schulte
2014-08-23 11:03 ` Ernesto Durante
2014-08-25 16:35 ` [PATCH] " Ernesto Durante
2014-08-28 14:46 ` Eric Schulte
2014-09-10 9:27 ` Achim Gratz
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=87lhqp7jnp.fsf@gmail.com \
--to=stobossey@gmail.com \
--cc=emacs-orgmode@gnu.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://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).