view release on metacpan or  search on metacpan

lib/Control/CLI/AvayaData.pm  view on Meta::CPAN

B<Publickey authentication> : If the remote host accepts it and the method was supplied with public/private keys. The public/private keys need to be in OpenSSH format. If the private key is protected by a passphrase then this must also be provided or...

=item *

B<Password authentication> : If the remote host accepts either 'password' or 'keyboard-interactive' authentication methods. A password must be provided or, if prompt_credentials is true, this method will prompt for the password. If password authentic...

=back


=item *

 view release on metacpan or  search on metacpan

lib/Control/CLI/Extreme.pm  view on Meta::CPAN

B<Publickey authentication> : If the remote host accepts it and the method was supplied with public/private keys. The public/private keys need to be in OpenSSH format. If the private key is protected by a passphrase then this must also be provided or...

=item *

B<Password authentication> : If the remote host accepts either 'password' or 'keyboard-interactive' authentication methods. A password must be provided or, if prompt_credentials is true, this method will prompt for the password. If password authentic...

=back


=item *

 view release on metacpan or  search on metacpan

lib/Control/CLI.pm  view on Meta::CPAN

B<Publickey authentication> : If the remote host accepts it and the method was supplied with public/private keys. The public/private keys need to be in OpenSSH format. If the private key is protected by a passphrase then this must also be provided or...

=item *

B<Password authentication> : If the remote host accepts either 'password' or 'keyboard-interactive' authentication methods. A password must be provided or, if prompt_credentials is true, this method will prompt for the password. If password authentic...

=back

There are some devices, with a crude SSH implementation, which will accept an SSH connection without any SSH authentication, and then perform an interactive login, like Telnet does. In this case, the connect() method, will not perform any SSH authent...

 view release on metacpan or  search on metacpan

lib/ControlFreak/Tutorial.pod  view on Meta::CPAN

for ruby/python you have to implement a proxy in this language (which
is not very complicated).

Because we don't want to load a tons of stuff in C<cfkd> process, and because
we want to keep C<cfkd> very stable anyway, we use an intermediary process:
a Proxy, whose job is to transparently manage a bunch of children services
as if they were directly under C<cfkd> control.

(TODO: example)

=head1 SECURITY

 view release on metacpan or  search on metacpan

ucpp/README  view on Meta::CPAN

   with the notations \u and \U. ucpp also accepts (with the proper
   flag) the UTF-8 encoding in the source file for such characters.
-- #include_next directive: it works as a #include, but will look
   for files only in the directories specified in the include path
   after the one the current file was found. This is a GNU-ism that
   is useful for writing transparent wrappers around header files.

Assertions and unicode are activated by specific flags; the #include_next
support is always active.

The ucpp code itself should be compatible with any ISO-C90 compiler.

 view release on metacpan or  search on metacpan

lib/Convert/Ethiopic/System.pm  view on Meta::CPAN

#                         LGRPP.  For these companion fonts in a font group the real TrueType name is applied in
#                         these fields for the purpose of document decoding.
#
#	TrueType Name      :  The typeface name of the font as seen in font menus, "face" attributes and RTF files.
#                         "Bold" and "Italic" versions of fonts are not included as the OS will make the names
#                         transparent.  The names _are_ added in the case that the encoding of the font changes.
#
#                         For output systems where this does not apply 'none' may be entered or the field is
#                         recycled to store a LibEth processing "option".
#
#   LibEth Enueration  :  The enumerated value of the encoding system within LibEth.

 view release on metacpan or  search on metacpan

i-term.tbx  view on Meta::CPAN

          <admin type="source">ISO 00639-3 : 2007</admin>
          <descrip type="definition">Alt.def: non-spoken special language characterized by rules that were explicitly established prior to its use</descrip>
          <admin type="source">ResearchSee the Comment (editor) field.</admin>
          <note/>
          <note/>
          <note>Note: An example of an artificial language is binary notation (for computer programming).&#13;&#13;Note that there is no context sentence in the ISO documents provided for the term formalized language. The term does, however, appear i...
          <transacGrp>
            <transac type="transactionType">origination</transac>
            <transacNote type="responsibility">HÃ¥vard Hjulstad (haavard)</transacNote>
            <date>2007-03-05 21:29:05</date>
          </transacGrp>

i-term.tbx  view on Meta::CPAN

          <admin type="source"/>
          <descrip type="definition">Alt.def: language characterized by words and expressions that are used in a variety of daily situations</descrip>
          <admin type="source">Research</admin>
          <note/>
          <note/>
          <note>Student:&#13;Note: General-language words and expressions often have multiple meanings depending on the situation, as well as multiple synonyms within a given situation.&#13;&#13;Note that the term language for general purposes does n...
          <transacGrp>
            <transac type="transactionType">origination</transac>
            <transacNote type="responsibility">Emma Harries (emma)</transacNote>
            <date>2008-11-29 19:05:16</date>
          </transacGrp>

i-term.tbx  view on Meta::CPAN

            <termNote type="termType"/>
            <termNote type="administrativeStatus"/>
            <termNote type="pronunciation"/>
            <note/>
            <note/>
            <descrip type="context">When the combining of words involves an essential characteristic from the intension of the concept, the compound is considered a transparent term.</descrip>
            <admin type="source">ISO 00704 : 2000</admin>
          </tig>
        </langSet>
        <langSet xml:lang="fr" id="cid142">
          <descrip type="definition"/>

i-term.tbx  view on Meta::CPAN

          <admin type="source">ISO 01087-1 : 2000</admin>
          <descrip type="definition">Alt.def: language used in a particular subject area or field and characterized by fixed terms</descrip>
          <admin type="source">ResearchSee the Comment (editor) field.</admin>
          <note>The specific linguistic means of expression always include subject-specific terminology and phraseology and also may cover stylistic or syntactic features. [ISO 1087-1:2000]&#13;&#13;[ISO/WD 29383-1 has the following definition:&#13;l...
          <note/>
          <note>Note: Special language avoids the use of synonyms for terms. Each concept in a special language should ideally be represented by only one term.&#13;&#13;Note: A special language can also be characterized by field-specific stylistic an...
          <transacGrp>
            <transac type="transactionType">origination</transac>
            <transacNote type="responsibility">built-in account (administrator)</transacNote>
            <date>2005-07-29 13:29:25</date>
          </transacGrp>

i-term.tbx  view on Meta::CPAN

            <termNote type="termType"/>
            <termNote type="administrativeStatus"/>
            <termNote type="pronunciation"/>
            <note/>
            <note/>
            <descrip type="context">Especially in newly emerging fields, the creation of such local equivalents is very important and may require prudent discussion among experts. The new term should be concise, for it is expected to serve as a mothe...
            <admin type="source">ISO/DIS 10241-2</admin>
          </tig>
        </langSet>
      </termEntry>
      <termEntry id="aid1186">

 view release on metacpan or  search on metacpan

doc/HISTORY  view on Meta::CPAN

- xxdecoding was broken because of over-tolerant uudecoding
- uudecoding was broken because of over-tolerant uudecoding :(

 0.4.15 (20.01.1996)
--------
- Implemented my own version of fgets() that allows to transparently read
  lines terminated either with LF (Unix), CRLF (DOS) or CR (Mac). Sadly,
  it's slower than the original.
- in previous versions, I have very much relaxed the checking for uudecoded
  lines (valid_data()). Now I only allow the less strong code (meaning,
  allow the data look more weird, more off the specs) if I'm sure it actually

 view release on metacpan or  search on metacpan

lib/Convos/public/packed/convos-05be7c5708ec2b607a1f50e9e1ad83ae.css  view on Meta::CPAN

  padding: 0;
  border: 0;
  font-size: 100%;
  line-height: 1.6em;
  vertical-align: baseline;
  background: transparent; }

article, aside, figure, footer, header, hgroup, nav, section, details, summary {
  display: block; }

ul {

lib/Convos/public/packed/convos-05be7c5708ec2b607a1f50e9e1ad83ae.css  view on Meta::CPAN

a {
  margin: 0;
  padding: 0;
  vertical-align: baseline;
  background: transparent; }

abbr[title], dfn[title] {
  border-bottom: 1px dotted #000;
  cursor: help; }

lib/Convos/public/packed/convos-05be7c5708ec2b607a1f50e9e1ad83ae.css  view on Meta::CPAN

      border-bottom: 1px solid #ddd;
      max-height: 400px; }
      .gist .gist-file .gist-data .line-data {
        padding: .5em !important; }
      .gist .gist-file .gist-data .line-pre {
        background: transparent !important;
        border: none !important;
        margin: 0 !important;
        padding: 0 !important; }
      .gist .gist-file .gist-data .gist-highlight {
        background: transparent !important; }
      .gist .gist-file .gist-data .line-numbers {
        background-color: #ececec;
        color: #aaa;
        border-right: 1px solid #ddd;
        text-align: right;

lib/Convos/public/packed/convos-05be7c5708ec2b607a1f50e9e1ad83ae.css  view on Meta::CPAN

  div.sidebar-right.active {
    right: 0;
    z-index: 997; }
  form.sidebar-right button.link,
  div.sidebar-right button.link {
    background: transparent;
    border: 0;
    width: 100%;
    padding: 6px 8px;
    text-align: left;
    display: block;

lib/Convos/public/packed/convos-05be7c5708ec2b607a1f50e9e1ad83ae.css  view on Meta::CPAN

body.tactile {
  height: 100%;
  background: #e7e7e7 url(../image/tactile-body-bg.png) 0 0 repeat; }

.landing-page {
  background: transparent url(../image/tactile-highlight-bg.jpg) 50% 0 no-repeat;
  min-height: 100%; }
  .landing-page .row {
    margin: auto;
    padding-top: 1em;
    width: 680px; }

 view release on metacpan or  search on metacpan

lib/CopyTree/VendorProof.pm  view on Meta::CPAN

=back

The lsoption is passed to the SUPER class fdls_ret, and is not handled at this level.  

The $startpath should be standardized to start in a certain 'root' directory; for example, in SharePoint::SOAPHandler, it must start with "Shared Documents", and in Livelink::DAV, it must start with a dir right under the webdav root folder.  Spaces a...

This method will generate @files and @dirs, which are lists of files and directories that start with $startpath, And returns 
	
	$self -> SUPER::fdls_ret ($lsoption, \@files, \@dirs),

 view release on metacpan or  search on metacpan

lib/Coro/ProcessPool.pm  view on Meta::CPAN

  while (my $result = $pipe->next) {
    ...
  }

All arguments to C<pipeline()> are passed transparently to the constructor of
L<Coro::ProcessPool::Pipeline>. There is no limit to the number of pipelines
which may be created for a pool.

=head1 A NOTE ABOUT IMPORTS AND CLOSURES

 view release on metacpan or  search on metacpan

Coro/LWP.pm  view on Meta::CPAN

Basically the same as above, distinction unclear. :)

=item L<AnyEvent::HTTP::LWP::UserAgent>

A different user agent implementation, not completely transparent to
users, requires Coro.

=back

=head1 DESCRIPTION

 view release on metacpan or  search on metacpan

README.pm  view on Meta::CPAN

There are many implementations for the CouchDB interface on CPAN.
Some are really old (may still work), and all are very thin: CouchDB uses
JSON over HTTP, which can be made to work with two lines of Perl.  However,
this leaves a lot of work to the applications which use that thin interface.
For instance, error handling, type handling, and server release differences.
The module traies to handle this all transparently.  See M<Couch::DB/DETAILS>
for more.

## Development &rarr; Release

Important to know, is that I use an extension on POD to write the manuals.

 view release on metacpan or  search on metacpan

lib/Couchbase/Bucket.pm  view on Meta::CPAN

=head4 Storage Format

By default, the document is serialized and stored as JSON. This allows proper
integration with other optional functionality of the cluster (such as views and
N1QL queries). You may also store items in other formats which may then be
transparently serialized and deserialized as needed.

To specify the storage format for a document, specify the `format` setting
in the L<Couchbase::Document> object, like so:

    use Couchbase::Document;

 view release on metacpan or  search on metacpan

XS.pm  view on Meta::CPAN

funny/weird/dumb stuff).

This is useful when you want to do the encoding yourself (e.g. when you
want to have UTF-16 encoded JSON texts) or when some other layer does
the encoding for you (for example, when printing to a terminal using a
filehandle that transparently encodes to UTF-8 you certainly do NOT want
to UTF-8 encode your data first and have Perl encode it another time).

=item C<utf8> flag enabled

If the C<utf8>-flag is enabled, C<encode>/C<decode> will encode all

 view release on metacpan or  search on metacpan

include/bearssl_ssl.h  view on Meta::CPAN

 * `force` parameter is non-zero, then an empty record is assembled and
 * marked for sending. In all other cases, this function does nothing.
 *
 * Empty records are technically legal, but not all existing SSL/TLS
 * implementations support them. Empty records can be useful as a
 * transparent "keep-alive" mechanism to maintain some low-level
 * network activity.
 *
 * \param cc      SSL engine context.
 * \param force   non-zero to force sending an empty record.
 */

 view release on metacpan or  search on metacpan

lib/Crypt/CBC.pm  view on Meta::CPAN

can be useful if, for example, you wish to place the encrypted in an
email message.

=head2 filehandle()

This method returns a filehandle for transparent encryption or
decryption using Christopher Dunkle's excellent L<Crypt::FileHandle>
module. This module must be installed in order to use this method.

filehandle() can be called as a class method using the same arguments
as new():

lib/Crypt/CBC.pm  view on Meta::CPAN

Printing to a filehandle opened for writing will encrypt the
data. Filehandles opened for input will be decrypted.

Here is an example:

  # transparent encryption
  open $fh,'>','encrypted.out' or die $!;
  print $fh "You won't be able to read me!\n";
  close $fh;

  # transparent decryption
  open $fh,'<','encrypted.out' or die $!;
  while (<$fh>) { print $_ }
  close $fh;

=head2 get_initialization_vector()

 view release on metacpan or  search on metacpan

t/01-main.t  view on Meta::CPAN

  is($v->encode('AttackAtDawn'), 'LxfopvEfRnhr', 'encode text case');
  $v->reset;
  is($v->decode('LxfopvEfRnhr'), 'AttackAtDawn', 'decode text case');
}

{ # text transparently passes through chars other than A-Z
  my $v = Crypt::Cipher::Vigenere->new('LeMoN');
  is($v->encode(q{⚔️ Attaque à l'aube!}), q{⚔️ Lxfodfi à x'ohmi!}, 'encode transparency');
  $v->reset;
  is($v->decode(q{⚔️ Lxfodfi à x'ohmi!}), q{⚔️ Attaque à l'aube!}, 'decode transparency');
}

 view release on metacpan or  search on metacpan

lib/Crypt/FileHandle.pm  view on Meta::CPAN

=head1 DESCRIPTION

This package creates a tied FileHandle that automatically encrypts or
decrypts data using the provided cipher. The FileHandle returned from
new() can be treated like a normal FileHandle. All encrypting,
decrypting, and buffering is completely transparent to the caller.

=head1 CIPHER METHODS

This package generally supports ciphers compliant with Crypt::CBC,
including CryptX ciphers. The cipher provided to new() must support

lib/Crypt/FileHandle.pm  view on Meta::CPAN

The number of encrypted bytes written to the real FileHandle may not
be the same as the number of cleartext bytes processed, especially if
a full block of data has not yet been provided. WRITE() will return
the number of cleartext bytes processed, which keeps the encryption
transparent to the caller.

=item F<READLINE()>

=item F<READ()>

lib/Crypt/FileHandle.pm  view on Meta::CPAN

READSIZE bytes. Any data that is read and decrypted but not returned
is stored in an internal buffer to be utilized by future read calls.

READ() will return the number of cleartext bytes processed and not
the actual number of bytes read from the real FileHandle, which keeps
the decryption transparent to the caller.

=item F<TELL()>

Called when tell() is called on the tied FileHandle returned from
new(). Returns the number of cleartext bytes processed through the
tied FileHandle. It does not return the position of the real
FileHandle, which may differ because of the encryption. The logical
position of the data is returned as if a normal FileHandle was used,
which keeps the encryption and decryption transparent to the caller.

=item F<CLOSE()>

Called when close() is called on the tied FileHandle returned from
new(). It closes the real FileHandle. If the real FileHandle was

 view release on metacpan or  search on metacpan

lib/Crypt/HSXKPasswd/Dictionary/ES.pm  view on Meta::CPAN

    'transmutáis',
    'transmuté',
    'transmutéis',
    'transmutó',
    'transo',
    'transparenta',
    'transparente',
    'transparentó',
    'transpira',
    'transpiraba',
    'transpiraban',
    'transpirabas',
    'transpirad',

 view release on metacpan or  search on metacpan

matrixssl-1-8-6-open/examples/sslSocket.c  view on Meta::CPAN

}

/******************************************************************************/
/*
	An example socket sslRead implementation that handles the ssl handshake
	transparently.  Caller passes in allocated buf and length. 
	
	Return codes are as follows:

	-1 return code is an error.  If a socket level error, error code is
		contained in status parameter.  If using a non-blocking socket

 view release on metacpan or  search on metacpan

lib/Crypt/OpenPGP/Message.pm  view on Meta::CPAN

    my @pieces = $msg->pieces;

=head1 DESCRIPTION

I<Crypt::OpenPGP::Message> provides a container for a sequence of PGP
packets. It transparently handles ASCII-armoured messages, as well as
cleartext signatures.

=head1 USAGE

=head2 Crypt::OpenPGP::Message->new( %arg )

 view release on metacpan or  search on metacpan

pqclean/.clang-tidy  view on Meta::CPAN

    value:           ''
  - key:             modernize-use-noexcept.UseNoexceptFalse
    value:           '1'
  - key:             modernize-use-nullptr.NullMacros
    value:           'NULL'
  - key:             modernize-use-transparent-functors.SafeMode
    value:           '0'
  - key:             modernize-use-using.IgnoreMacros
    value:           '1'
  - key:             objc-forbidden-subclassing.ForbiddenSuperClassNames
    value:           'ABNewPersonViewController;ABPeoplePickerNavigationController;ABPersonViewController;ABUnknownPersonViewController;NSHashTable;NSMapTable;NSPointerArray;NSPointerFunctions;NSTimer;UIActionSheet;UIAlertView;UIImagePickerController...

 view release on metacpan or  search on metacpan

lib/Crypt/Sodium/XS/OO/secretstream.pm  view on Meta::CPAN

L<Crypt::Sodium::XS::secretstream> can be used to securely send an ordered
sequence of messages to a peer. Since the length of the stream is not limited,
it can also be used to encrypt files regardless of their size.

It transparently generates nonces and automatically handles key rotation.

=head1 CONSTRUCTOR

=head2 new

 view release on metacpan or  search on metacpan

lib/Crypt/XkcdPassword/Words/EN.pm  view on Meta::CPAN

who're
whaddya
welsh
vitamin
viper
transparent
surprisingly
sunglasses
starring
stanford
spears

 view release on metacpan or  search on metacpan

ext/xxHash/xxhash.h  view on Meta::CPAN

#  endif
#endif

#ifdef XXH_DOXYGEN
/*!
 * @brief Emulate a namespace by transparently prefixing all symbols.
 *
 * If you want to include _and expose_ xxHash functions from within your own
 * library, but also want to avoid symbol collisions with other libraries which
 * may also include xxHash, you can use XXH_NAMESPACE to automatically prefix
 * any public symbol from xxhash library with the value of XXH_NAMESPACE

 view release on metacpan or  search on metacpan

Simp.pm  view on Meta::CPAN

                  echos  _HOUR    %_HOUR%;    &
                  echos  _MINUTE  %_MINUTE%;  &
                  echos  _SECOND  %_SECOND%;`; while($data =~ s/(_[BCDFHKMRSY][ABEGIOW][ACDHLNUWY]?[IORSTU]?[HMNT]?[DEN]?S?)\s+([^;]*);//){ $SDAT{$1} = $2; }
      return; # raw() allows ^C,^S,^Z 2simply pass thru,unlike cbreak(),but raw requirz`reset`from the cmdline,if the app crashes; napms($ms) 2nap millisecs;
    } initscr();noecho();nonl();raw();start_color();$GLBL{'FLAGUDCL'} = eval('use_default_colors(); 1') || 0;
    # start_color without use_default_colors was making transparent GnomeTerminal BackGround solid blacK; A7QAMqt: ... but since use_default_colors() above is
    #   not defined in some SunOS/Solaris Curses libraries, I've wrapped it in an eval to hopefully pass their CPAN tests; # below: nodelay()||timeout(-1)...
    curs_set(0);keypad(1);meta(1);intrflush(0);notimeout(0);timeout(0);clear();move(getmaxy()-1,getmaxx()-1);refresh();    # ... for non||blocking getch()
    @BORDSETS = ( # initscr initializes line-draw chars for my border hash
      { 'ul' => ACS_ULCORNER,                  'ur' => ACS_URCORNER,
                     'rt' => ACS_RTEE,  'lt' => ACS_LTEE,

 view release on metacpan or  search on metacpan

test.pl  view on Meta::CPAN

BEGIN { $| = 1; print "1..last_test_to_print\n"; }
END { print "not ok 1\n" unless $loaded; }

use CzFast qw ( &czregexp &czrecode );

$str = 'Seriál krok za krokem vysvìtluje vše potøebné pro tvorbu webovských stránek -- zejména popis jazyka HTML a dalších potøebných dovedností jako tvorba klikacích map, transparentních a animovaných obrázkù atd.';

print "Following text is in windows-1250 encoding, you'll se it corrupted:\n";
print "$str\n\n";

##############################################################################

 view release on metacpan or  search on metacpan

Chart.pm  view on Meta::CPAN

	dpink	=> [255,105,180],
	marine	=> [127,127,255],
	cyan	=> [0,255,255],
	lbrown	=> [210,180,140],
	dbrown	=> [165,42,42],
	transparent => [1,1,1]
);

our @dfltcolors = qw( red green blue yellow purple orange
dblue cyan dgreen lbrown );

Chart.pm  view on Meta::CPAN

				if ($t=~/<\d+>/);
			$t = lc $t;
			$props{$prop} = $t,
			next
				if (check_color($t) ||
					(($prop eq 'BACKGROUND') && ($t eq 'transparent')));

			return ($dbh->DBI::set_err(-1, "Invalid value for $prop property.",'S1000'), $t);
		}

 		if (($prop eq 'COLOR') || ($prop eq 'SHAPE') || ($prop eq 'FONT')) {

 view release on metacpan or  search on metacpan

DtfSQL.pm  view on Meta::CPAN

distinguishes between integer (IV), double (NV) and string (PV) scalar types. Thus, there is indeed a 
difference in retrieving data with the retrieval type set to DTF_CT_CSTRING or set to DTF_CT_DEFAULT.

However, for calculations with retrieved data, it makes no great difference (except for the decimal type) if 
you retrieve a field value as string or as stored in the database with attention to its actual datatype: The 
scalars will contain either numbers or strings. In general, conversion from one form to another is transparent, 
i.e. happens automatically in Perl. This should be suitable even for the decimal datatype when retrieved as 
string, because it is converted to a scalar holding a floating point number in arithmetical operations (although 
the accuracy may suffer).
  
Note (4): If you retrieve data of type decimal, you will get back a *decimal object* in $fieldVal-- see