public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [OT] - Code translation tools?
Date: Mon, 24 Jan 2011 17:15:30 -0800	[thread overview]
Message-ID: <AANLkTimpAAbe8nvTwDSkQrEA9se235v2D8Eh6oXFnJiJ@mail.gmail.com> (raw)
In-Reply-To: <ihl5s1$jra$1@dough.gmane.org>

On Mon, Jan 24, 2011 at 4:35 PM, walt <w41ter@gmail.com> wrote:
> On 01/24/2011 02:34 PM, Mark Knecht wrote:
>>
>> Hello,
>>    I'm wondering if there are any generic sorts of code translation
>> tools in portage wherein I could translate from an 'uncommon' language
>> no one here is likely to use (EasyLanguage) into C?
>>
>>    As an example I've attached a little EL function...
>
> Can't give you a real answer, but that code looks very much like Pascal.
> Reminds me of a misspent youth.
>

In 1983 I certainly wasn't a turbo user of Turbo Pascal either... ;-)

> Is there a definite reason for choosing C instead of something else, e.g.
> python?  Just idle curiosity, nothing more.
>

I'm interested in learning a bit about CUDA as an evaluation platform
and the tools from NVidia are based around C. (As best I understand.)

> If I knew a wee bit more about m4 I'm sure I could do it with that alone.
> But I'd need to do actual work to learn m4, which is not likely to happen...
>

Thanks!

- Mark



  reply	other threads:[~2011-01-25  1:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 22:34 [gentoo-user] [OT] - Code translation tools? Mark Knecht
2011-01-25  0:35 ` [gentoo-user] " walt
2011-01-25  1:15   ` Mark Knecht [this message]
2011-01-26  1:15 ` [gentoo-user] " Michael Orlitzky
2011-01-26 17:56   ` Mark Knecht
2011-01-26 18:47     ` Michael Orlitzky
2011-01-26 19:40       ` Mark Knecht
2011-01-26 20:32         ` Michael Orlitzky
2011-01-26 21:54           ` Mark Knecht

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

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

  git send-email \
    --in-reply-to=AANLkTimpAAbe8nvTwDSkQrEA9se235v2D8Eh6oXFnJiJ@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.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