dunyakirkali

dunyakirkali

I am trying to implement a parser.

I want to parse a string that has the following format:

I did the following:

  sample =
    empty()
    |> ascii_string([?A..?Z, ?0..?9], 2)
    |> ascii_string([0..127], 4)
    |> ascii_string([0..127], 4)
    |> ignore(string("$"))

  defparsec :parse, sample

As much as I like it, something tells me that it can be cleaner / more consice.

Any ideas?

Showing Posts 1 to 9

kip

kip

ex_cldr Core Team

EDIT: I misread the protocol version part which is not hex … taking another stab

I think in this simple case a binary decomposition will be more straight forward:

case some_string do
  <<version::binary-6, count::binary-4, "$">> ->
    version = String.to_integer(version, 16)
    count = String.to_integer(count, 16)
    {:ok, version, count}
  _other ->
    {:error, :invalid}
end
kip

kip

ex_cldr Core Team

OK, revised version. Not sure its any more “beautiful” than your version but may be food for thought:

case some_string do
  <<h1::integer-8, h2::integer-8, version::binary-4, count::binary-4, "$">> 
      when (h1 in ?A..?Z or h1 in ?0..?9) and (h2 in ?A..?Z or h2 in ?0..?9)->
    header = List.to_string [h1, h2]
    version = String.to_integer(version, 16)
    count = String.to_integer(count, 16)
    {:ok, header, version, count}
  _other ->
    {:error, :invalid}
end
dunyakirkali

dunyakirkali OP

Thnx for the reply @kip

The reason I chose for nimble_parsec is because, down the line, there are many more commands that I have to implement where some have variable byte lenghts for some of the paramters and I don’t want to type those all out. I’d rather use nimble_parse for that.

Here is an example

kip

kip

ex_cldr Core Team

Using nimble_parsec I tend to prefer using a helper module for combinators rather than inline. I also tend to create semantic functions because sooner or later debugging a nimble_parsec combinator - and providing reasonable messages back to a user on parse errors - becomes a challenge.

Example parser

This is a pattern I usually follow, here just parsing your first example.

defmodule Parse.Helpers do
  import NimbleParsec

  def version() do
    head()
    |> concat(hex_integer(4))
    |> label("version")
    |> tag(:version)
  end

  def hex_integer(digits) do
    ascii_string([?a..?f, ?A..?F, ?0..?9], digits)
    |> reduce(:hex_to_integer)
  end

  def count() do
    hex_integer(4)
    |> label("count")
    |> unwrap_and_tag(:count)
  end

  def head() do
    ascii_string([?A..?Z, ?0..?9], 2)
    |> label("head")
  end

  def tail() do
    string("$")
    |> label("tail")
    |> unwrap_and_tag(:tail)
  end

  def hex_to_integer([string]) do
    String.to_integer(string, 16)
  end

end

defmodule Parser do
  import NimbleParsec
  import Parse.Helpers

  defparsec :parse,
    version()
    |> concat(count())
    |> concat(tail())

end

Example usage

iex> Parser.parse "AB98761234$"
{:ok, [version: ["AB", 39030], count: 4660, tail: "$"], "", %{}, {1, 0}, 11}

iex> Parser.parse "AB98761234" 
{:error, "expected version, followed by count, followed by tail", "AB98761234",
 %{}, {1, 0}, 0}
kip

kip

ex_cldr Core Team

Noting BTW that you can use binary pattern matching to parse variable length content. This article has a really good example for parsing PNG files.

dunyakirkali

dunyakirkali OP

Thnx a lot @kip ! :heart:

You’ve thought me so much with this one example.

dunyakirkali

dunyakirkali OP

@kip One last question:

There are several commands in this protocol that I need to parse.
They all have a different starting string that identifies them.

Which of the following paths would you suggest I use:

a) Using binary pattern matching then routing into a nimble_parsec parser

...
  defparsec(
    :parse_sack,
    |> ignore(string(","))
    |> concat(version())
    |> ignore(string(","))
    |> concat(count())
    |> concat(tail())
  )

  defparsec(
    :parse_ack,
    |> ignore(string(","))
    |> concat(version())
    |> ignore(string(","))
    |> concat(imei())
    |> ignore(string(","))
    |> concat(device_name())
    |> ignore(string(","))
    |> concat(ble_command_password())
    |> ignore(string(","))
    |> concat(generated_time())
    |> ignore(string(","))
    |> concat(count_number())
    |> concat(tail())
  )

  def parse(<<"+ACK:GTHBD", rest::binary()>>), do: parse_ack(rest)
  def parse(<<"+SACK:GTHBD", rest::binary()>>), do: parse_sack(rest)

b) using pure nimble_parsec with something like option

kip

kip

ex_cldr Core Team

Given you’re heading down the nimble_parsec route I would stay in that domain and do something like:

defparsec :parse,
  choice([
    string("+ACK:GTHBD") |> parsec(:parse_ack),
    string("+SACK:GTHBD") |> parsec(:parse_sack)
  ])
end
dunyakirkali

dunyakirkali OP

Awesome!

Thnx a lot @kip

— All posts loaded —

Where Next? Top

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
water
I’m aware of 2 such projects, are there others? git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
katta
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
peck
Hi everyone. My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
bradley
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
unaware8150
Hello folks! So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
Alvinkariuki
How Can I Optimise Compile Time Dependencies I have been building an elixir application for about 2 years now. Many modules and files ha...
New

Other Trending Topics Top

mudasobwa
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
KristerV
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
juhalehtonen
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
budgie
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with. But I don’t use it anymore. Serverless was the promis...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews