This module provides a utility method, "to_identifier" for converting
an arbitrary string into a readable representation using the ASCII
subset of "\w" for use as an identifier in a computer program. The
intent is to make unique identifier names from which the content
of the original string can be easily inferred by a human just by
reading the identifier.
If you need the full set of "\w" including Unicode, see the subclass
String::ToIdentifier::EN::Unicode.
Currently, this process is one way only, and will likely remain
this way.
The default is to create camelCase identifiers, or you may pass in
a separator char of your choice such as "_".
Binary char groups will be separated by "_" even in camelCase
identifiers to make them easier to read, e.g.: "foo_2_0xFF_Bar".
The module is a probability based, corpus-trained tagger that assigns
POS tags to English text based on a lookup dictionary and a set of
probability values. The tagger assigns appropriate tags based on
conditional probabilities - it examines the preceding tag to determine
the appropriate tag for the current word. Unknown words are classified
according to word morphology or can be set to be treated as nouns
or other parts of speech. The tagger also extracts as many nouns
and noun phrases as it can, using a set of regular expressions.
The exportable subroutines of Lingua::EN::Inflect provide
plural inflections, "a"/"an" selection for English words,
and manipulation of numbers as words.
For the theory of Memoization, please see the Memoize module
documentation. This module implements an expiry policy for Memoize
that follows LRU semantics, that is, the last n results, where n
is specified as the argument to the CACHESIZE parameter, will be
cached.
This module always exports a single function, Dumper, which can be
called with an array of values to dump those values.
It exists, fundamentally, as a convenient way to reproduce a set
of Dumper options that we've found ourselves using across large
numbers of applications, primarily for debugging output.
The principle guiding theme is "all the concision you can get while
still having a useful dump and not doing anything cleverer than
setting Data::Dumper options" - it's been pointed out to us that
Data::Dump::Streamer can produce shorter output with less lines of
code. We know. This is simpler and we've never seen it segfault.
But for complex/weird structures, it generally rocks. You should
use it as well, when Concise is underkill. We do.
Why is deparsing on when the aim is concision? Because you often
want to know what subroutine refs you have when debugging and because
if you were planning to eval this back in you probably wanted to
remove subrefs first and add them back in a custom way anyway. Note
that this -does- force using the pure perl Dumper rather than the
XS one, but I've never in my life seen Data::Dumper show up in a
profile so "who cares?".
Because the many-to-many relationships are not real relationships,
they can not be introspected with DBIx::Class. Many-to-many
relationships are actually just a collection of convenience methods
installed to bridge two relationships. This DBIx::Class component
can be used to store all relevant information about these
non-relationships so they can later be introspected and examined.
Farstream is a video conferencing connection manager for the Telepathy
framework. This component enables the use of Telepathy instant messaging
clients with Farstream/Nice servers.
ok aja@
The Farstream (formerly Farsight) project is an effort to create a
framework to deal with all known audio/video conferencing protocols. On
one side it offers a generic API that makes it possible to write plugins
for different streaming protocols, on the other side it offers an API
for clients to use those plugins.
(farsight2 is dead, long live farstream!)
ok aja@
These flags types were originally incorrectly handled in glib as being
enums. That bug was fixed, but they're still enums here, leading to
warnings about the mismatch.
Change them to flags.
