ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ConTeXt ML <ntg-context@ntg.nl>
Subject: Re: [.tuc] oddity when storing a table
Date: Sun, 16 Sep 2012 23:16:28 +0200	[thread overview]
Message-ID: <505641AC.9040404@wxs.nl> (raw)
In-Reply-To: <20120916171741.GB1240@phlegethon>

On 16-9-2012 19:17, Philipp Gesang wrote:
> Hi all,
>
> I can’t explain the following behavior of the .tuc writer. When
> passed a nested hash, context fails on the second pass if the
> array part of the first nesting depth is empty:
>
> ·······································································
>
> %% the commented lines work
> \startluacode
>    job.variables.tobesaved.foo = { bar = {  } }
>    -- job.variables.tobesaved.foo = { "works now",  bar = {  } }
>    -- job.variables.tobesaved.foo = { bar =  "works too" }
> \stopluacode
>
> \starttext foo \stoptext
>
> ·······································································
>
> I get this error:
>
> ·······································································
>    ! LuaTeX error ...text/tex/texmf-context/tex/context/base/cldf-ini.lua:410: no string to print
>    stack traceback:
>      [C]: in function 'flush'
>      ...text/tex/texmf-context/tex/context/base/cldf-ini.lua:410: in function <...text/tex/texmf-context/tex/context/base/cldf-ini.lua:360>
>      (tail call): ?
>      ...text/tex/texmf-context/tex/context/base/core-uti.lua:112: in function 'initializer'
>      ...text/tex/texmf-context/tex/context/base/core-uti.lua:200: in function 'load'
>      ...text/tex/texmf-context/tex/context/base/core-uti.lua:66: in function 'initialize'
>      <main ctx instance>:1: in main chunk.
>
>    system          > tex > error on line 1 in file /home/phg/context/tex/texmf-context/tex/context/base/cont-yes.mkiv: LuaTeX error  ...
> ·······································································
>
> Bug?

no, feature. job variables are just key/values and accessible at the tex 
end (you store 'works too' in 'bar')

if you want arbitrary data to be stores you need to used datasets, as 
explained in

http://wiki.contextgarden.net/Command/definedataset

-----------------------------------------------------------------
                                           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
___________________________________________________________________________________


  reply	other threads:[~2012-09-16 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-16 17:17 Philipp Gesang
2012-09-16 21:16 ` Hans Hagen [this message]
2012-09-17 21:13   ` Philipp Gesang
2012-09-17 22:19     ` Hans Hagen

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=505641AC.9040404@wxs.nl \
    --to=pragma@wxs.nl \
    --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).