Re: [NTG-context] LuaJitTeX, \texenginename, and \texengineversion
On 2013–05–07 Kip Warner wrote: I find the \texenginename and \texengineversion useful for retrieving the backend name and version. They work fine when using the vanilla LuaTeX backend. However, when using LuaJitTeX, the aforementioned macros still seem to retrieve LuaTeX specific information and not LuaJitTeX - unless I'm doing something wrong. This is by design, see http://comments.gmane.org/gmane.comp.tex.luatex/3000 Marco signature.asc Description: Digital signature ___ 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 ___
Re: [NTG-context] LuaJitTeX, \texenginename, and \texengineversion
On Wed, May 8, 2013 at 2:49 AM, Kip Warner k...@thevertigo.com wrote:
Hey Luigi,
I find the \texenginename and \texengineversion useful for retrieving
the backend name and version. They work fine when using the vanilla
LuaTeX backend. However, when using LuaJitTeX, the aforementioned
macros still seem to retrieve LuaTeX specific information and not
LuaJitTeX - unless I'm doing something wrong. I was careful to ensure I
passed --engine=luajittex to context as well.
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com
yes, it's known and it's ok, because luajittex is not different from
luatex as luatex is different from pdftex/xetex/etex
(and if it's so, then it is an error).
A quick check could be
\startluacode
if jit==nil then print(=This is not luajitTeX) else
print(=You are running luajitTeX ) end
\stopluacode
of course one can write a global
jit ={} also in luatex.
Another one used in the log is
\startluacode
print(===..string.lower(status.banner))
\stopluacode
and you can search for luajittex .
My wish is that luajittex should be 100% compatible with luatex, but
unfortunately there are some differences between lua5.1 used by luajit2.0
and lua5.2
that makes this wish currently impossible to satisfied at engine level ---
ConTeXt is smart enough to manage these differences, but you can still
write
a lua script that is valid for lua5.2 but not for luajit2.0, see for
example
http://lua-users.org/lists/lua-l/2010-03/msg00237.html
Full compatibility between lua5.2 and luajit2.0, for what I see, is not on
the top on the Mike Pall's agenda.
--
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
___
Re: [NTG-context] LuaJitTeX, \texenginename, and \texengineversion
On Wed, May 8, 2013 at 9:32 AM, luigi scarso luigi.sca...@gmail.com wrote: yes, it's known and it's ok, because luajittex is not different from luatex as luatex is different from pdftex/xetex/etex (and if it's so, then it is an error). (and if it's not so, then it is an error). -- 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 ___
Re: [NTG-context] LuaJitTeX, \texenginename, and \texengineversion
On 5/8/2013 9:29 AM, Marco Patzer wrote: On 2013–05–07 Kip Warner wrote: I find the \texenginename and \texengineversion useful for retrieving the backend name and version. They work fine when using the vanilla LuaTeX backend. However, when using LuaJitTeX, the aforementioned macros still seem to retrieve LuaTeX specific information and not LuaJitTeX - unless I'm doing something wrong. This is by design, see http://comments.gmane.org/gmane.comp.tex.luatex/3000 Marco For context, the most we benefit from luajittex is the lua vm speed and not jitting. If you need to check for luatex vs luajittex then you're doing things that are dependent on specific luajit features (like ffi) and that's non-portable (platforms as well as the future). Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] LuaJitTeX, \texenginename, and \texengineversion
On Wed, 2013-05-08 at 09:32 +0200, luigi scarso wrote:
On Wed, May 8, 2013 at 2:49 AM, Kip Warner k...@thevertigo.com wrote:
Hey Luigi,
I find the \texenginename and \texengineversion useful for retrieving
the backend name and version. They work fine when using the vanilla
LuaTeX backend. However, when using LuaJitTeX, the aforementioned
macros still seem to retrieve LuaTeX specific information and not
LuaJitTeX - unless I'm doing something wrong. I was careful to ensure I
passed --engine=luajittex to context as well.
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com
yes, it's known and it's ok, because luajittex is not different from
luatex as luatex is different from pdftex/xetex/etex
(and if it's so, then it is an error).
A quick check could be
\startluacode
if jit==nil then print(=This is not luajitTeX) else
print(=You are running luajitTeX ) end
\stopluacode
of course one can write a global
jit ={} also in luatex.
Another one used in the log is
\startluacode
print(===..string.lower(status.banner))
\stopluacode
and you can search for luajittex .
My wish is that luajittex should be 100% compatible with luatex, but
unfortunately there are some differences between lua5.1 used by luajit2.0
and lua5.2
that makes this wish currently impossible to satisfied at engine level ---
ConTeXt is smart enough to manage these differences, but you can still
write
a lua script that is valid for lua5.2 but not for luajit2.0, see for
example
http://lua-users.org/lists/lua-l/2010-03/msg00237.html
Full compatibility between lua5.2 and luajit2.0, for what I see, is not on
the top on the Mike Pall's agenda.
Thanks Luigi. That was pretty comprehensive.
For my purposes, it makes no different to me whether I am using luatex
or luajittex. However, in my document's front matter I like to have
general information about the tools used to typeset the document, and
for that reason I thought it would be nice if there was a simple and
elegant way to show which backend was used.
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com
signature.asc
Description: This is a digitally signed message part
___
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
___
