Parsing expressions with combinators












1














I'm very new to Haskell's ReadP library, and the entire concept of parser combinators, so I was wondering whether there are better ways to do some things in this program:



import Text.ParserCombinators.ReadP
import Control.Applicative
import Data.List

data Operator = Add | Subtract

instance Show Operator where
show Add = "+"
show Subtract = "-"

instance Read Operator where
readsPrec _ "+" = [(Add, "")]
readsPrec _ "-" = [(Subtract, "")]
readsPrec _ _ =

data Expression = Number Int
| Infix { left :: Expression, op :: Operator, right :: Expression }

instance Show Expression where
show (Number x) = show x
show (Infix left op right) = "(" ++ (show left) ++ " " ++ (show op) ++ " " ++ (show right) ++ ")"

digit :: ReadP Char
digit = satisfy $ char -> char >= '0' && char <= '9'

number :: ReadP Expression
number = fmap (Number . read) (many1 digit)

operator :: ReadP Operator
operator = fmap read (string "+" <|> string "-")

expression :: ReadP Expression
expression = do
skipSpaces
left <- number
skipSpaces
op <- Control.Applicative.optional operator
case op of
Nothing -> return left
Just op -> do
skipSpaces
right <- expression
return (Infix left op right)

parseExpression :: String -> Maybe Expression
parseExpression input = case readP_to_S expression input of
-> Nothing
xs -> (Just . fst . last) xs


The main area where I'm looking for improvements is the expression function, and specifically the things which seem improvable are the repeated calls to skipSpaces and the case expression to check whether an operator was parsed, but of course if you notice anything else that would be helpful too!










share|improve this question







New contributor




Zac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    1














    I'm very new to Haskell's ReadP library, and the entire concept of parser combinators, so I was wondering whether there are better ways to do some things in this program:



    import Text.ParserCombinators.ReadP
    import Control.Applicative
    import Data.List

    data Operator = Add | Subtract

    instance Show Operator where
    show Add = "+"
    show Subtract = "-"

    instance Read Operator where
    readsPrec _ "+" = [(Add, "")]
    readsPrec _ "-" = [(Subtract, "")]
    readsPrec _ _ =

    data Expression = Number Int
    | Infix { left :: Expression, op :: Operator, right :: Expression }

    instance Show Expression where
    show (Number x) = show x
    show (Infix left op right) = "(" ++ (show left) ++ " " ++ (show op) ++ " " ++ (show right) ++ ")"

    digit :: ReadP Char
    digit = satisfy $ char -> char >= '0' && char <= '9'

    number :: ReadP Expression
    number = fmap (Number . read) (many1 digit)

    operator :: ReadP Operator
    operator = fmap read (string "+" <|> string "-")

    expression :: ReadP Expression
    expression = do
    skipSpaces
    left <- number
    skipSpaces
    op <- Control.Applicative.optional operator
    case op of
    Nothing -> return left
    Just op -> do
    skipSpaces
    right <- expression
    return (Infix left op right)

    parseExpression :: String -> Maybe Expression
    parseExpression input = case readP_to_S expression input of
    -> Nothing
    xs -> (Just . fst . last) xs


    The main area where I'm looking for improvements is the expression function, and specifically the things which seem improvable are the repeated calls to skipSpaces and the case expression to check whether an operator was parsed, but of course if you notice anything else that would be helpful too!










    share|improve this question







    New contributor




    Zac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      1












      1








      1







      I'm very new to Haskell's ReadP library, and the entire concept of parser combinators, so I was wondering whether there are better ways to do some things in this program:



      import Text.ParserCombinators.ReadP
      import Control.Applicative
      import Data.List

      data Operator = Add | Subtract

      instance Show Operator where
      show Add = "+"
      show Subtract = "-"

      instance Read Operator where
      readsPrec _ "+" = [(Add, "")]
      readsPrec _ "-" = [(Subtract, "")]
      readsPrec _ _ =

      data Expression = Number Int
      | Infix { left :: Expression, op :: Operator, right :: Expression }

      instance Show Expression where
      show (Number x) = show x
      show (Infix left op right) = "(" ++ (show left) ++ " " ++ (show op) ++ " " ++ (show right) ++ ")"

      digit :: ReadP Char
      digit = satisfy $ char -> char >= '0' && char <= '9'

      number :: ReadP Expression
      number = fmap (Number . read) (many1 digit)

      operator :: ReadP Operator
      operator = fmap read (string "+" <|> string "-")

      expression :: ReadP Expression
      expression = do
      skipSpaces
      left <- number
      skipSpaces
      op <- Control.Applicative.optional operator
      case op of
      Nothing -> return left
      Just op -> do
      skipSpaces
      right <- expression
      return (Infix left op right)

      parseExpression :: String -> Maybe Expression
      parseExpression input = case readP_to_S expression input of
      -> Nothing
      xs -> (Just . fst . last) xs


      The main area where I'm looking for improvements is the expression function, and specifically the things which seem improvable are the repeated calls to skipSpaces and the case expression to check whether an operator was parsed, but of course if you notice anything else that would be helpful too!










      share|improve this question







      New contributor




      Zac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      I'm very new to Haskell's ReadP library, and the entire concept of parser combinators, so I was wondering whether there are better ways to do some things in this program:



      import Text.ParserCombinators.ReadP
      import Control.Applicative
      import Data.List

      data Operator = Add | Subtract

      instance Show Operator where
      show Add = "+"
      show Subtract = "-"

      instance Read Operator where
      readsPrec _ "+" = [(Add, "")]
      readsPrec _ "-" = [(Subtract, "")]
      readsPrec _ _ =

      data Expression = Number Int
      | Infix { left :: Expression, op :: Operator, right :: Expression }

      instance Show Expression where
      show (Number x) = show x
      show (Infix left op right) = "(" ++ (show left) ++ " " ++ (show op) ++ " " ++ (show right) ++ ")"

      digit :: ReadP Char
      digit = satisfy $ char -> char >= '0' && char <= '9'

      number :: ReadP Expression
      number = fmap (Number . read) (many1 digit)

      operator :: ReadP Operator
      operator = fmap read (string "+" <|> string "-")

      expression :: ReadP Expression
      expression = do
      skipSpaces
      left <- number
      skipSpaces
      op <- Control.Applicative.optional operator
      case op of
      Nothing -> return left
      Just op -> do
      skipSpaces
      right <- expression
      return (Infix left op right)

      parseExpression :: String -> Maybe Expression
      parseExpression input = case readP_to_S expression input of
      -> Nothing
      xs -> (Just . fst . last) xs


      The main area where I'm looking for improvements is the expression function, and specifically the things which seem improvable are the repeated calls to skipSpaces and the case expression to check whether an operator was parsed, but of course if you notice anything else that would be helpful too!







      parsing haskell






      share|improve this question







      New contributor




      Zac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      Zac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      Zac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked Jan 3 at 18:01









      Zac

      1061




      1061




      New contributor




      Zac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Zac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Zac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes











          Your Answer





          StackExchange.ifUsing("editor", function () {
          return StackExchange.using("mathjaxEditing", function () {
          StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
          StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
          });
          });
          }, "mathjax-editing");

          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "196"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          Zac is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f210830%2fparsing-expressions-with-combinators%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Zac is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Zac is a new contributor. Be nice, and check out our Code of Conduct.













          Zac is a new contributor. Be nice, and check out our Code of Conduct.












          Zac is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Code Review Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          Use MathJax to format equations. MathJax reference.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f210830%2fparsing-expressions-with-combinators%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Terni

          A new problem with tex4ht and tikz

          Sun Ra