8 # same terms as Perl itself.  If in doubt, 
70   # 'usethreads' works around a bug in threadperl having to do with
126       # default is that we make up an in-memory hash
136   # both get merged to the same in-memory hash.
152   # We should put some more stuff in here eventually.
154   # And you know what?  More stuff keeps going in!
264       # Maybe in a later version we can use a faster test.
339   $DEBUG and warn "${name}($fn) => $cref in _make_cref\n";
346     croak "Function `$funcname' called in forbidden $context context; faulting";
348     croak "Anonymous function called in forbidden $context context; faulting";
392 does this by caching the return values of the function in a table.
394 jumps in and gives you the value out of the table, instead of letting
420 time it needs to, and then save the result in a table.  Then if you
452 program would look in a certain direction, figure out what it was
458       # Figure out which object is in direction $direction
464 Since there are relatively few objects in a picture, there are only a
471 functions in this package are None of Your Business.
480 At present, there are no non-fatal errors, but there might be some in
545 program arguments into a string in a way that equivalent arguments
574 28 in between.  (In ASCII, this is called FS or control-\.)  This
605 than those in its arguments.  Suppose you have a function which
622 current hour in the normalizer:
628 function will treat its arguments differently in list context than it
629 would in scalar context, you can have the normalizer function select
630 its behavior based on the results of C<wantarray>.  Even if called in
643 When your function is called in scalar context, its return value is
644 cached in one hash, and when your function is called in list context,
645 its value is cached in the other hash.  You can control the caching
663 C<MEMORY> means that return values from the function will be cached in
674 on-disk database, so that cached values are stored in the database and
685 This has the effect of storing the cache in a C<DB_File> database
686 whose name is in C<$filename>.  The cache will persist after the
690 runs in the background and populates the cache file.  Then when you
697 aid in the debugging of old programs that use it.  Old programs should
712 C<FAULT> means that you never expect to call the function in scalar
716 	`foo' function called in forbidden list context at line ...
717 	`foo' function called in forbidden scalar context at line ...
722 and sclar context, and that return values in both contexts should be
724 return values should be stored in the same hash that is used for
733 Normally, the following code will result in two calls to C<pi>:
739 The first call caches the value C<3> in the scalar cache; the second
740 caches the list C<(3)> in the list cache.  The third call doesn't call
752 stored in the same disk file; this saves you from having to deal with
770 This normalizer function will store scalar context return values in
792 version in the first place, including making the name refer to the
804 expired, see the documentation for C<Memoize::Expire>, included in
813 as its cache.  Then you can examine or modify the hash at any time in
881 reference to the users list will be stored in the memo table.  C<main>
912 number in the hash is necessarily going to take a lot longer than a
931 C<SDBM_File> doesn't supply an C<EXISTS> method, so included in this
934 cache table on disk in an C<SDBM_File> database:
944 it's on the disk.  So if you want to store your cache table in a
946 front-end onto C<Storable>.  The hash table is actually kept in
958 in `network order'.  (See L<Storable> for more details about this.)
965 See Memoize::Expire, which is a plug-in module that adds expiration
967 that Memoize::Expire implements, it is easy to write your own plug-in
978 in Perl, and until it is resolved, memoized functions will see a
984 memoized and the cache is in a C<DB_File> database, then the value of
1001 memoization and about the internals of Memoize that appeared in The
1002 Perl Journal, issue #13.  (This article is also included in the
1006 topics) in tremendous detail.  It will be published by Morgan Kaufmann
1007 in 2002, possibly under the title I<Perl Advanced Techniques
1034 under threaded Perl, to Alex Dudkevich for reporting the bug in
1040 'C<flush_cache> function, and to Jenda Krynicky for being a light in
1044 this module in the core and for his patient and helpful guidance

Indexes created Tue Jul 24 14:28:13 CEST 2018