From: nalaginrut <nalaginrut@gmail.com>
To: CRLF0710 <crlf0710@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: New feature proposal: Support C-code inline?
Date: Mon, 25 Apr 2011 09:33:04 +0800 [thread overview]
Message-ID: <1303695184.2684.15.camel@Renee-desktop> (raw)
In-Reply-To: <BANLkTinaRFc5z5DFvhE-jecwfLOLSv0gjw@mail.gmail.com>
> Well, is the code a piece of string ? Does that mean we'll have code
> generation on-the-fly facilities? ^_^
>
yes. you don't need to convert var's type, this module does it automatic
for you.
> By the way, do you like the idea of some kind of inline C-code
> "segments" embed in scm files? (Just like preprocessor blocks in C)
I think there're many new ideas worth trying, and your "C-code segment
embedded" is good for designing some bigger hybrid programming with
C&guile(this C-code inline is better for small code embedded). We may
add more convenient feature, for a instance, typedef/include/C macro.
But as I said, this simple solution is a temporary substitute before AOT
compiler came out. Embedded big C-code into guile program is not a good
idea. If we really want to do that, the better way is to write an
extension just like Guile always does.
--
GNU Powered it
GPL Protected it
GOD Blessed it
HFG - NalaGinrut
--hacker key--
v4sw7CUSMhw6ln6pr8OSFck4ma9u8MLSOFw3WDXGm7g/l8Li6e7t4TNGSb8AGORTDLMen6g6RASZOGCHPa28s1MIr4p-x hackerkey.com
---end key---
next prev parent reply other threads:[~2011-04-25 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 9:50 New feature proposal: Support C-code inline? nalaginrut
2011-04-22 20:14 ` Noah Lavine
2011-04-23 4:24 ` nalaginrut
[not found] ` <BANLkTinaRFc5z5DFvhE-jecwfLOLSv0gjw@mail.gmail.com>
2011-04-25 1:33 ` nalaginrut [this message]
2011-04-26 10:11 ` William ML Leslie
2011-05-05 17:04 ` nalaginrut
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.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1303695184.2684.15.camel@Renee-desktop \
--to=nalaginrut@gmail.com \
--cc=crlf0710@gmail.com \
--cc=guile-devel@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.
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).