From 29e8f402e563f88c4e988315de5b8e705459896e Mon Sep 17 00:00:00 2001 From: Evan Sparks Date: Fri, 8 Jul 2016 23:13:26 -0700 Subject: [PATCH] Update UniformAccessPrinciple.scala Correcting confusing grammatical error. --- src/main/scala/stdlib/UniformAccessPrinciple.scala | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/scala/stdlib/UniformAccessPrinciple.scala b/src/main/scala/stdlib/UniformAccessPrinciple.scala index 0ced9849..1c310b5b 100644 --- a/src/main/scala/stdlib/UniformAccessPrinciple.scala +++ b/src/main/scala/stdlib/UniformAccessPrinciple.scala @@ -9,7 +9,7 @@ object UniformAccessPrinciple extends FlatSpec with Matchers with org.scalaexerc /** The Scala language implements a programming concept known as the [Uniform Access Principle](http://en.wikipedia.org/wiki/Uniform_access_principle) which was first put forth by Bertrand Meyer, inventor of the Eiffel programming language. * - * This principle states that variables and parameterless functions should be accessed using the same syntax. Scala supports this principle by not allowing parentheses to be placed at call sites of parameterless functions. As a result, a parameterless function definition can be changed to a val, or vice versa, without affecting client code. + * This principle states that variables and parameterless functions should be accessed using the same syntax. Scala supports this principle by allowing parentheses to not be placed at call sites of parameterless functions. As a result, a parameterless function definition can be changed to a val, or vice versa, without affecting client code. * */ def uniformAccessPrincipleUniformAccessPrinciple(res0: Int, res1: Int) {