Skip to main content
Software Engineering

Return to Question

retagged functional programming
Link
edit approved Nov 30, 2014 at 14:37
अज्ञ
edit approved Nov 30, 2014 at 14:37
अज्ञ
  • 101
  • 4
I don't think the meaning "cause a programmer to lose control" is clear enough on its own without specifying what he loses control over. So I've re-added that information.
Source Link
sepp2k
sepp2k
  • 4.3k
  • 1
  • 28
  • 25

It seems lazy evaluation of expressions can cause a programmer to lose control over the order in which their code is executed. I am having trouble understanding why this would be acceptable or desired by a programmer.

How can this paradigm be used to build predictable software that works as intended, when we have no guarantee when and where an expression will be evaluated?

It seems lazy evaluation of expressions can cause a programmer to lose control. I am having trouble understanding why this would be acceptable or desired by a programmer.

How can this paradigm be used to build predictable software that works as intended, when we have no guarantee when and where an expression will be evaluated?

It seems lazy evaluation of expressions can cause a programmer to lose control over the order in which their code is executed. I am having trouble understanding why this would be acceptable or desired by a programmer.

How can this paradigm be used to build predictable software that works as intended, when we have no guarantee when and where an expression will be evaluated?

Made wording more clear. Feel free to more accurately clarify sentiment of OP with a better edit.
Source Link
edit approved Nov 23, 2012 at 16:23
samthebrand
edit approved Nov 23, 2012 at 16:23
samthebrand
  • 368
  • 2
  • 12
  • 27

It seems Lazylazy evaluation of expressions willcan cause the designer of a given piece of codeprogrammer to lose control over the sequence their code is executed. I am having trouble understanding why this would be acceptable or even desired by a programmer.

How can this paradigm be used to build predictable software that works as intended, when we have no guarantee when and where an expression will be evaluated?

Lazy evaluation of expressions will cause the designer of a given piece of code lose control over the sequence their code is executed. I am having trouble understanding why this would be acceptable or even desired by a programmer.

How can this paradigm be used to build predictable software that works as intended, when we have no guarantee when and where an expression will be evaluated?

It seems lazy evaluation of expressions can cause a programmer to lose control. I am having trouble understanding why this would be acceptable or desired by a programmer.

How can this paradigm be used to build predictable software that works as intended, when we have no guarantee when and where an expression will be evaluated?

added 63 characters in body
Source Link
gnat
gnat
  • 20.5k
  • 29
  • 117
  • 309
Tweeted twitter.com/#!/StackProgrammer/status/243906710798999552
Post Migrated Here from stackoverflow.com (revisions)
Source Link
z_axis
z_axis