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

AI_POLICY.md  view on Meta::CPAN

---

## Overview

This document describes how artificial intelligence tools are used in the maintenance and development of this project. It is intended to be transparent with our contributors, users, and the broader open-source community about the role AI plays — an...

We believe in honest, clear communication about AI-assisted workflows. This policy will be updated as our practices evolve.

---

 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

AI_POLICY.md  view on Meta::CPAN

---

## Overview

This document describes how artificial intelligence tools are used in the maintenance and development of this project. It is intended to be transparent with our contributors, users, and the broader open-source community about the role AI plays — an...

We believe in honest, clear communication about AI-assisted workflows. This policy will be updated as our practices evolve.

---

 view release on metacpan or  search on metacpan

lib/Crypt/Sodium/XS/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

The constructor is called with the C<Crypt::Sodium::XS-E<gt>secretstream>
method.

 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

 * @brief Exposes the implementation without marking functions as inline.
 */
#  define XXH_PRIVATE_API
#  undef XXH_PRIVATE_API
/*!
 * @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 @ref XXH_NAMESPACE to automatically prefix
 * any public symbol from xxhash library with the value of @ref 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

 view release on metacpan or  search on metacpan

Firebird.pm  view on Meta::CPAN

=item * DESCRIBE

Provides information about columns that are retrieved by a DSQL statement,
or about placeholders in a statement. This functionality is supported by the
driver, and transparent for users. Column names are available via
$sth->{NAME} attributes.

=item * EXECUTE IMMEDIATE

Calling do() method without bind value(s) will do the same.

 view release on metacpan or  search on metacpan

Illustra.pm  view on Meta::CPAN

    }

Due to the limitations in the Illustra API, it is not
possible to support reading large objects from each row, as they are fetched.
This means that future versions of DBD::Illustra will never be able to
transparently return large objects with normal column data. However, you can
cast large object values to large_text, in which case they will be returned
as normal values.

=head1 AUTHOR

 view release on metacpan or  search on metacpan

InterBase.pm  view on Meta::CPAN

=item * DESCRIBE

Provides information about columns that are retrieved by a DSQL statement,
or about placeholders in a statement. This functionality is supported by the
driver, and transparent for users. Column names are available via
$sth->{NAME} attributes.

=item * EXECUTE IMMEDIATE

Calling do() method without bind value(s) will do the same.

 view release on metacpan or  search on metacpan

lib/DBD/Multi.pm  view on Meta::CPAN

=head1 DESCRIPTION

This software manages multiple database connections for failovers and also
simple load balancing.  It acts as a proxy between your code and your database
connections, transparently choosing a connection for each query, based on your
preferences and present availability of the DB server.

This module is intended for read-only operations (where some other application
is being used to handle replication).

 view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

  to ODBC 2.0 drivers (why are you still using ODBC 2.0 drivers?).
  From now on DBD::ODBC needs to be linked with an ODBC Driver Manager
  and I recommend unixODBC on UNIX and the MS ODBC Driver Manager
  on Windows. There are really good reasons for this but mainly it
  is because an ODBC Driver Manager will map ODBC 2.0 calls to an
  ODBC 3.0 driver and vice versa and handle UNICODE transparently.

  Bumped Test::Simple requirement up to 0.90 so we can use done_testing
  and note.

  Bump Perl requirement to 5.8 as per DBI.

 view release on metacpan or  search on metacpan

lib/DBD/Oracle.pm  view on Meta::CPAN

When fetching LOBs with this interface a 'LOB Locator' is created then used to get the lob with the LongReadLen and LongTruncOk attributes.
The value for 'LongReadLen' is dependent on the version and settings of the Oracle DB you are using. In theory it ranges from 8GBs
in 9iR1 up to 128 terabytes with 11g but you will also be limited by the physical memory of your PERL instance.

When inserting or updating LOBs some I<major> magic has to be performed
behind the scenes to make it transparent.  Basically the driver has to
insert a 'LOB Locator' and then refetch the newly inserted LOB
Locator before being able to write the data into it.  However, it works
well most of the time, and I've made it as fast as possible, just one
extra server-round-trip per insert or update after the first.  For the
time being, only single-row LOB updates are supported.

 view release on metacpan or  search on metacpan

debian/changelog  view on Meta::CPAN

 -- Rainer Weikusat <rweikusat@talktalk.net>  Thu, 03 Jul 2025 10:37:59 +0100

libdbd-pg-async-perl (0.5) unstable; urgency=medium

  * make dbh cancel method work in face of asychronous operations
    transparently issued by the driver

 -- Rainer Weikusat <rweikusat@talktalk.net>  Thu, 03 Jul 2025 10:00:53 +0100

libdbd-pg-async-perl (0.4.2) unstable; urgency=medium

  * fixed pg_db_result to work as documented in face of asychronous
    statements transparently issued by the driver

 -- Rainer Weikusat <rweikusat@talktalk.net>  Thu, 26 Jun 2025 19:16:47 +0100

libdbd-pg-async-perl (0.4.1) unstable; urgency=medium

 view release on metacpan or  search on metacpan

lib/DBD/PgLite.pm  view on Meta::CPAN

  my $get_nid = "SELECT NEXTVAL('news_news_id_seq')";
  my $news_id = $dbh->selectrow_array($get_nid);

=head1 DESCRIPTION

The module automatically and transparently transforms a broad range of
SQL statements typical of PostgreSQL into a form suitable for use in
SQLite. This involves both (a) parsing and filtering of the SQL; and
(b) the addition of several PostgreSQL-compatible functions to SQLite.

Mainly because of datatype issues, support for many PostgreSQL

 view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

1.12
	- Brought up to date with SQLite 3.3.5

1.11
    - Make blobs work transparently (without SQLBLOB binding)

1.10
    - Fix Unicode support (DOMQ)
    - Support usleep on all Linux (inc. debian) (DOMQ)
    - Upgrade to sqlite 3.2.7

 view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

1.12
	- Brought up to date with SQLite 3.3.5

1.11
    - Make blobs work transparently (without SQLBLOB binding)

1.10
    - Fix Unicode support (DOMQ)
    - Support usleep on all Linux (inc. debian) (DOMQ)
    - Upgrade to sqlite 3.2.7

 view release on metacpan or  search on metacpan

lib/DBD/SQLite2.pm  view on Meta::CPAN

Returns either "UTF-8" or "iso8859" to indicate how the SQLite library was compiled.

=item sqlite_handle_binary_nulls

Set this attribute to 1 to transparently handle binary nulls in quoted
and returned data.

B<NOTE:> This will cause all backslash characters (C<\>) to be doubled
up in all columns regardless of whether or not they contain binary
data or not. This may break your database if you use it from another