Skip to content
Browse files

Don't use Nil to mean () anymore

  • Loading branch information...
1 parent b841b9c commit 948f48a8eb17bc6289923b1499033ef45f193a18 @TimToady TimToady committed
Showing with 4 additions and 4 deletions.
  1. +4 −4 S32-setting-library/Containers.pod
View
8 S32-setting-library/Containers.pod
@@ -19,8 +19,8 @@ DRAFT: Synopsis 32: Setting Library - Containers.pod
Created: 19 Feb 2009 extracted from S29-functions.pod
- Last Modified: 22 May 2013
- Version: 39
+ Last Modified: 13 Jul 2013
+ Version: 40
If you read the HTML version, it is generated from the Pod in the specs
repository under
@@ -208,8 +208,8 @@ categorized by the mapper into the category of the associated key.
Unlike C<classify>, C<categorize> always assumes that the return
value of the mapper is a list of categories that are appropriate to
-the current value. Hence, if the mapper returns C<Nil>, the value
-is discarded rather than being returned under a C<Nil> key. On the
+the current value. Hence, if the mapper returns C<()>, the value
+is discarded rather than being stored under any key. On the
other hand, if the mapper returns a list of categories, the value in
question will be pushed into multiple hash locations (while C<classify>
would merely make a key out of the list returned from the mapper).

0 comments on commit 948f48a

Please sign in to comment.
Something went wrong with that request. Please try again.