ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "luigi scarso" <luigi.scarso@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: [LUATEX] uname() volunteers needed
Date: Thu, 22 May 2008 15:50:47 +0200	[thread overview]
Message-ID: <fe8d59da0805220650u37b1ca1do551e72c4b27c2afd@mail.gmail.com> (raw)
In-Reply-To: <48355726.7090301@elvenkind.com>

On Thu, May 22, 2008 at 1:21 PM, Taco Hoekwater <taco@elvenkind.com> wrote:
>
> Hi,
>
> Yue Wang wrote:
>>
>> I think it is better to only return a table while calling the Lua
>> function. The table contains key=value pairs for
>> {sysname=,nodename=,release=, version=,machine=}. For Windows, you
>> just fill these names by hand instead(easy, isn't it?).
>
> Easy to say, sure. You are not on windows either, I assume?
>
> Anyway, 0.30.0 will have both the old and the new ( os.uname()
> function), and the old variables will not go away until 0.40.0.
>
>> LuaTeX is going public in
>> months, so before that every major API change is OK to the developers.
>> After public, changing APIs will make other developers unhappy.
>
> I do not know what you are referring to. Nothing in the API is
> fixed until 1.0.0, and that is still a few years off !
hmm, we must what david says about that, see
http://granthinam.blogspot.com/search/label/Conference report
"Kastrup, one of the developers of LuaTeX,"

:))))))))))))))


-- 
luigi
it's new .
it's powerful .
it's luatex .
http://www.luatex.org
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-05-22 13:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 12:11 Taco Hoekwater
2008-05-21 12:25 ` Thomas A. Schmitz
2008-05-21 12:59   ` Yue Wang
2008-05-21 13:44     ` Thomas A. Schmitz
2008-05-21 12:43 ` Jin-Hwan Cho
2008-05-21 13:43 ` Arthur Reutenauer
2008-05-21 14:26   ` Yue Wang
2008-05-21 20:22   ` Martin Schröder
2008-05-21 22:00     ` Arthur Reutenauer
2008-05-21 22:15       ` Martin Schröder
2008-05-21 23:59         ` Arthur Reutenauer
2008-05-22 10:26       ` Yue Wang
2008-05-22 11:21         ` Taco Hoekwater
2008-05-22 13:50           ` luigi scarso [this message]
2008-05-22 14:11             ` Hans Hagen
2008-05-22 14:18               ` luigi scarso
2008-05-22 11:28         ` Hans Hagen
2008-05-21 18:40 ` Peter Münster
2008-05-21 19:42 ` Diego Depaoli
2008-05-21 20:09 ` Gour
2008-05-21 20:35   ` Michael Hallgren
2008-05-22 12:22 ` Taco Hoekwater
2008-05-22 23:39 ` [LUATEX] " Mojca Miklavec

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=fe8d59da0805220650u37b1ca1do551e72c4b27c2afd@mail.gmail.com \
    --to=luigi.scarso@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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 NNTP newsgroup(s).