From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Script to automatically generate typescripts
Date: Fri, 4 Jun 2010 10:23:55 +0200 [thread overview]
Message-ID: <AANLkTikG3jNx0_xs5-5C-6py68-tmj3wKEr1ADsolAt7@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimVXNc7kfnFJtkHDCdsiJCzVsxNNR094v7Aot4C@mail.gmail.com>
On Fri, Jun 4, 2010 at 10:03 AM, Mojca Miklavec
<mojca.miklavec.lists@gmail.com> wrote:
> On Fri, Jun 4, 2010 at 09:32, luigi scarso wrote:
>>
>> 2) why python ? We have lua in luatex; mkiv has a lot of lua code about fonts.
>
> Hmmm ... the guy who spent most of his time in community trying to
> make python work with ConTeXt is now complaining about the programming
> language? Come on ... :)
I'm not say that it's wrong.
It's the same as if I write a lua script to do "XYZ" for Plone: why ?
There are a lot of python code in Plone that probably can be used to do "XYZ".
>
> Whenever I write something I use the language I master most (even if
> it's not the most suitable language for that task), so I guess that
> must be the reason. But if the script proves to be useful, it's still
> short enough that anyone could convert it to Lua to get rid of
> dependencies on yet another language.
A python's programmer has no problem to write a lua version
(and a javascript programmer too, as Mathias Nater showed to me)
The key point here is the dependency on another language:
for luatex it's almost useless
to use a scripting/dynamic language other than lua
(I hope one day we will end without ruby and perl for mkiv too, if reasonable) .
Of course perl, ruby. python,<put_your_favorite_language_here>
are all goods programming languages
but mixing them together not always make a good pie .
--
luigi
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-06-04 8:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 16:51 Michael Murphy
2010-06-04 7:32 ` luigi scarso
2010-06-04 8:03 ` Mojca Miklavec
2010-06-04 8:23 ` luigi scarso [this message]
2010-06-04 10:27 ` Hans Hagen
2010-06-04 8:37 ` Hans Hagen
2010-06-04 8:50 ` luigi scarso
2010-06-04 9:52 ` Michael Murphy
2010-06-04 10:00 ` Mojca Miklavec
2010-06-04 10:08 ` luigi scarso
2010-06-04 16:08 ` Michael Murphy
2010-06-04 16:19 ` Mojca Miklavec
2010-06-04 18:33 ` Hans Hagen
2010-06-04 10:01 ` luigi scarso
2010-06-04 10:21 ` Mojca Miklavec
2010-06-04 10:25 ` Hans Hagen
2010-06-04 10:29 ` luigi scarso
2010-06-04 11:16 ` Khaled Hosny
2010-06-04 16:05 ` Michael Murphy
2010-06-04 14:12 ` Vnpenguin
2010-06-07 10:59 ` Thomas Floeren
[not found] <mailman.1395.1275590320.4277.ntg-context@ntg.nl>
2010-06-03 21:33 ` Vyatcheslav Yatskovsky
2010-06-03 22:40 ` Michael Murphy
[not found] <mailman.1411.1275638618.4277.ntg-context@ntg.nl>
2010-06-04 9:26 ` Vyatcheslav Yatskovsky
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=AANLkTikG3jNx0_xs5-5C-6py68-tmj3wKEr1ADsolAt7@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).