From 2a129789adbfa64098cba50a27f88d9602d022ab Mon Sep 17 00:00:00 2001 From: Jeff Davidson Date: Tue, 9 Sep 2014 18:10:57 -0700 Subject: Update unclear Fragment Javadoc. "Empty" could imply that the constructor body itself is empty, which is not a requirement. All that matters is that the constructor is public and takes no arguments. Change-Id: Id1cda8835baee9f9ad89aba8b3d33b963e61e718 --- core/java/android/app/Fragment.java | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'core/java/android/app/Fragment.java') diff --git a/core/java/android/app/Fragment.java b/core/java/android/app/Fragment.java index 672ef7b..4374622 100644 --- a/core/java/android/app/Fragment.java +++ b/core/java/android/app/Fragment.java @@ -166,11 +166,12 @@ final class FragmentState implements Parcelable { * activity: if the activity is stopped, no fragments inside of it can be * started; when the activity is destroyed, all fragments will be destroyed. * - *

All subclasses of Fragment must include a public empty constructor. + *

All subclasses of Fragment must include a public no-argument constructor. * The framework will often re-instantiate a fragment class when needed, * in particular during state restore, and needs to be able to find this - * constructor to instantiate it. If the empty constructor is not available, - * a runtime exception will occur in some cases during state restore. + * constructor to instantiate it. If the no-argument constructor is not + * available, a runtime exception will occur in some cases during state + * restore. * *

Topics covered here: *

    -- cgit v1.1