symfony
diff --git a/‎UPGRADE-2.5.md
Lines changed: 42 additions & 1 deletion b/‎UPGRADE-2.5.md
Lines changed: 42 additions & 1 deletion
diff --git a/‎src/Symfony/Component/PropertyAccess/CHANGELOG.md
Line 8000 s changed: 4 additions & 0 deletions b/‎src/Symfony/Component/PropertyAccess/CHANGELOG.md
Line 8000 s changed: 4 additions & 0 deletions
diff --git a/‎src/Symfony/Component/PropertyAccess/Exception/InvalidArgumentException.php
Lines changed: 21 additions & 0 deletions b/‎src/Symfony/Component/PropertyAccess/Exception/InvalidArgumentException.php
Lines changed: 21 additions & 0 deletions
@@ -45,6 +45,47 @@ Form
    {
    ```
 
+PropertyAccess
+--------------
+
+ * The methods `isReadable()` and `isWritable()` were added to
+   `PropertyAccessorInterface`. If you implemented this interface in your own
+   code, you should add these two methods.
+
+ * The methods `getValue()` and `setValue()` now throw an
+   `NoSuchIndexException` instead of a `NoSuchPropertyException` when an index
+   is accessed on an object that does not implement `ArrayAccess`. If you catch
+   this exception in your code, you should adapt the catch statement:
+
+   Before:
+
+   ```php
+   $object = new \stdClass();
+
+   try {
+       $propertyAccessor->getValue($object, '[index]');
+       $propertyAccessor->setValue($object, '[index]', 'New value');
+   } catch (NoSuchPropertyException $e) {
+       // ...
+   }
+   ```
+
+   After:
+
+   ```php
+   $object = new \stdClass();
+
+   try {
+       $propertyAccessor->getValue($object, '[index]');
+       $propertyAccessor->setValue($object, '[index]', 'New value');
+   } catch (NoSuchIndexException $e) {
+       // ...
+   }
+   ```
+
+   A `NoSuchPropertyException` is still thrown when a non-existing property is
+   accessed on an object or an array.
+
 Validator
 ---------
 
@@ -56,7 +97,7 @@ Validator
 
    After:
 
-   Default email validation is now done via a simple regex which may cause invalid emails (not RFC compilant) to be 
+   Default email validation is now done via a simple regex which may cause invalid emails (not RFC compilant) to be
    valid. This is the default behaviour.
 
    Strict email validation has to be explicitly activated in the configuration file by adding
 
@@ -5,6 +5,10 @@ CHANGELOG
 ------
 
  * allowed non alpha numeric characters in second level and deeper object properties names
+ * [BC BREAK] when accessing an index on an object that does not implement
+   ArrayAccess, a NoSuchIndexException is now thrown instead of the
+   semantically wrong NoSuchPropertyException
+ * [BC BREAK] added isReadable() and isWritable() to PropertyAccessorInterface
 
 2.3.0
 ------
 
@@ -0,0 +1,21 @@
+<?php
+
+/*
+ * This file is part of the Symfony package.
+ *
+ * (c) Fabien Potencier <fabien@symfony.com>
+ *
+ * For the full copyright and license information, please view the LICENSE
+ * file that was distributed with this source code.
+ */
+
+namespace Symfony\Component\PropertyAccess\Exception;
+
+/**
+ * Base InvalidArgumentException for the PropertyAccess component.
+ *
+ * @author Bernhard Schussek <bschussek@gmail.com>
+ */
+class InvalidArgumentException extends \InvalidArgumentException implements ExceptionInterface
+{
+}