ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: lpdf.checkedkey has problem with false values
Date: Mon, 15 Sep 2014 19:12:02 +0200	[thread overview]
Message-ID: <54171DE2.3070008@wxs.nl> (raw)
In-Reply-To: <CALDha9MKm9fUdT_6tjtj7XC8gVP9rv+kEe9nzG0nLwUQG0Q0Ww@mail.gmail.com>

On 9/15/2014 6:12 PM, Michail Vidiassov wrote:
> Dear Aditya, Peter and All,
>
>> I think that what Peter meant was:
>
> the real issue is not teaching me lua and improving the style of my example,
> but my complaint (correct or not) about inability of lpdf.checkedkey

it looks like your question was not clear then

> to correctly fetch false boolean values: they are fetched as nil, just
> as if they were absent or of incorrect type.

well, they're just not treated special

> Please, someone with time and, preferably, authority - take a look at
> lpdf.checkedkey code (5 minutes maximum).
> Talking in general about lua, not knowing what lpdf.checkedkey is,
> does and is supposed to do, does not look like efficient use of time.

you can try this (untested)

function lpdf.checkedkey(t,key,variant)
     local pn = t and t[key]
     if pn then
         local tn = type(pn)
         if tn == variant then
             if variant == "string" then
                 return pn ~= "" and pn or nil
             elseif variant == "table" then
                 return next(pn) and pn or nil
             else
                 return pn
             end
         elseif tn == "string" then
             if variant == "number" then
                 return tonumber(pn)
             elseif variant == "boolean" then
                 return toboolean(pn)
             end
         end
     end
end

-----------------------------------------------------------------
                                           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:[~2014-09-15 17:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 14:14 Michail Vidiassov
2014-09-15 14:59 ` Peter Rolf
2014-09-15 15:34   ` Michail Vidiassov
2014-09-15 15:56     ` Aditya Mahajan
2014-09-15 16:12       ` Michail Vidiassov
2014-09-15 17:12         ` Hans Hagen [this message]
2014-09-15 18:25           ` Michail Vidiassov
2014-09-15 19:17             ` Hans Hagen
2014-09-16  3:33               ` Michail Vidiassov

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=54171DE2.3070008@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).