• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

kikito / inspect.lua / 112 / 2
98%
master: 99%

Build:
Build:
LAST BUILD BRANCH: safe-inspect
DEFAULT BRANCH: master
Ran 05 Apr 2019 08:08PM UTC
Files 3
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

05 Apr 2019 08:07PM UTC coverage: 97.539% (-1.0%) from 98.588%
LUA="lua=5.2"

Pull #45

travis-ci

web-flow
add a special case for NULL userdata

When interpreting userdata values using 'inspect', the numeric identifiers
are useful to match identify of pointers (comparing the low counters
like `<userdata 3> is easier than reading long pointers like
`userdata: 0x749abc39efa29`).

However, the `NULL` pointer is enough of a special case that it is
important to know when one of those numbered pointers happens to
be `NULL`. When one is dealing with things like JSON parsers, where
the only usual userdata is `cjson.null`, one gets accostumed over
time to interpret `<userdata 1>` to mean `NULL`. This is not obvious,
however, and a seasoned user will trip up the day another userdata
is used in the same table and `NULL` is now `<userdata 2>`.

Adding a test for this would require compiling and loading a C extension.
Pull Request #45: Improve output of userdata, handling`__tostring` and NULL

436 of 447 relevant lines covered (97.54%)

39.0 hits per line

Source Files on job 112.2 (LUA="lua=5.2")
  • Tree
  • List 0
  • Changed 3
  • Source Changed 2
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 102
  • Travis Job 112.2
  • 777c8d46 on github
  • Prev Job for LUA="lua=5.2" on tostring-userdata (#108.2)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc