Functional Programming

1398 readers

1 users here now

founded 1 year ago

MODERATORS

Ategon

cercerilla

How to convert imperative side-effectful program to functional (in Ocaml)? (lemy.lol)

submitted 9 months ago by [email protected] to c/functional_programming

7 comments fedilink hide all child comments

I've been enjoying learning ocaml, but I found it very easy to write code riddled with side effects and imperative-ness.

Take this example:

let some_func arg = 
  let input = format_input_from_stdin ()
  let read_content = read_file "some/file/path.txt"
  let to_write = get_write_file_content input read_content
  let () = write_file "some/other/path.txt" to_write 
  let output = run_external_command_with_output 
  (output, read_content)

As you can see, many side effects and imperative steps in the code. Is there a better practice for coding this in a functional manner?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 9 months ago (1 children)

Yea, in nearly every program we still need some amount of I/O which will violate a purely functional approach - we just try to isolate it as much as possible.

[–] [email protected] 1 points 9 months ago (2 children)

The Haskell approach is to use monads too, right? I can't seem to understand the benefit of the monad approach

[–] oessessnex 2 points 9 months ago* (last edited 9 months ago)

The way you can think of it is that in OCaml everything is implicitly wrapped in an IO monad. In Haskell the IO monad is explicit, so if a function returns something in IO you know it can perform input and output, in OCaml there is no way to tell just from the types. That means that in Haskell the code naturally stratifies into a part that does input and output and a pure core. In OCaml you can do the same thing, however it needs to be a conscious design decision.

[–] [email protected] 1 points 9 months ago

True Functional Programmers will probably correct my lack of nuance here, but my understanding is that the IO monad is basically just scribbling some category theory formalities on top of IO ops so that everything is still technically a pure function. You can think of the IO monad as representing the "state" of the rest of the universe outside of your program, which your program reads or modifies. As you pass through your monadic bind ops (i.e., as you read or write IO), the state is carried through implicitly and "modified" as appropriate. All functions, then, are just transforming data (i.e., either your program's data or the rest of the universe), so everything is pure.