# Workspace doesn't display UInt values

**URL:** <https://discourse.julialang.org/t/workspace-doesnt-display-uint-values/64073>\
**Category:** New to Julia\
**Tags:** juno\
**Created:** [July 5, 2021, 11:40am UTC](https://discourse.julialang.org/t/workspace-doesnt-display-uint-values/64073 "2021-07-05T11:40:51Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![sijo](https://avatars.discourse-cdn.com/v4/letter/s/da6949/32.png) [@sijo](https://discourse.julialang.org/u/sijo)\
**Post date:** [July 5, 2021, 1:17pm UTC](https://discourse.julialang.org/t/workspace-doesnt-display-uint-values/64073/9 "2021-07-05T13:17:17Z")

</div>

> [@jpmorr](#):
>
> For cursory checks, base-10 would be so much easier

I’m not sure… Typically, `Int` is used for variables that represent a size or count, where base 10 is more natural indeed, and `UInt` is often used for values where individual bits or bytes have a meaning.

There are good reasons for this… See a [recent discussion](https://discourse.julialang.org/t/why-int-instead-of-uint-for-indexing/63589) about why indices and `length` use `Int`.

Maybe it’s different in your case, but I see two masks in your list. Would they be more readable in base 10? (I guess not.)

For `full_timestep` maybe it would make sense to use an `Int`?

For `fileversion` it depends how the version is encoded… For example `0x00280212` could be the code for a version of the form “x.y” as two 16-bit values: `0x0028` and `0x0212`. This would arguably be less readable in base 10.

---

_[View the full topic](https://discourse.julialang.org/t/workspace-doesnt-display-uint-values/64073)._