Author:halw
Date:2010-08-14T15:09:37.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@655 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2010-08-14 15:09:37 +00:00
parent fd3d1eb1f0
commit 2b36669046

View File

@@ -84,7 +84,7 @@ This is no longer always true. If an instance of <code>SPECIAL</code> is created
However creating a <code>SPECIAL</code> using <code>make_filled</code> will produce an instance in which <code>count</code> and <code>capacity</code> are equal upon creation. So the behavior is similar to that of previous versions. Also, <code>make_filled</code> is available in both ''default'' and ''compatible'' modes.
If you are depending upon <code>count</code> and <code>capacity</code> having the same value, then use <code>make_filled</code> for creation. And then if you need resizing, use the "with_default" versions of the "resized" queries, specifically <code>resized_area_with_default</code> and <code>aliased_resized_area_with_default</code>.
If your code depends upon <code>count</code> and <code>capacity</code> having the same value, then you can use <code>make_filled</code> for creation. And then if you need resizing, use the "_with_default" versions of the "resized" features, specifically <code>resized_area_with_default</code> and <code>aliased_resized_area_with_default</code>.