# Is INTEGER! in PARSE Too Obfuscating?

**URL:** <https://revolt.metaeducation.com/forum/t/is-integer-in-parse-too-obfuscating/1578>\
**Category:** Parsing\
**Created:** [March 28, 2021, 5:29pm UTC](https://revolt.metaeducation.com/forum/t/is-integer-in-parse-too-obfuscating/1578 "2021-03-28T17:29:10Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![hostilefork](https://revolt.metaeducation.com/forum/user_avatar/revolt.metaeducation.com/hostilefork/32/421_2.png) [@hostilefork](https://revolt.metaeducation.com/forum/u/hostilefork)\
**Post date:** [July 11, 2022, 11:40pm UTC](https://revolt.metaeducation.com/forum/t/is-integer-in-parse-too-obfuscating/1578/11 "2022-07-11T23:40:19Z")

</div>

> [@BlackATTR](#):
>
> Having those integers floating around in rules can be a speed-bump when reading, and they're probably a hurdle for newbies.

With INTEGER! being a combinator that just evaluates to itself, it permits us to have a fairly literate SKIP combinator:

```
>> parse [a b "Much more literate!"] [skip 2, text!]
== "Much more literate!"

```

Actually makes sense...as opposed the historical **2 skip**. That required you absorbing that SKIP is an arity-0 function which you sometimes use to match ANY-VALUE! for SET rules... as well as that integers prefix a repeat count of the rule after it. Much clearer to say SKIP is a combinator that takes how much to skip!

🕶

> [@hostilefork](#):
>
> Maybe it's just my use cases. But I don't really find myself having literal numbers of times to run a rule very often.

So the exception I've found here is byte counts when parsing binary. Things that know how many bytes they want literally put those byte counts down.

But where I once did **`copy 2 skip`** in these cases, that had become **`across 2 <any>`**. But rather than robotically turn that into **`across repeat 2 <any>`** this just needs to go back to **`across skip 2`**.

Yet in truth...these cases all tend to suck...and what they actually want is something like @rgchris's [BINCODE](https://revolt.metaeducation.com/forum/t/bincode/1863), or ENBIN/DEBIN combinators. So I wouldn't have worried about it anyway.

---

_[View the full topic](https://revolt.metaeducation.com/forum/t/is-integer-in-parse-too-obfuscating/1578)._
