Free coupon codes software for linux

Convert::GeekCode is a Perl module that can convert and generate geek code sequences.

SYNOPSIS

use Convert::GeekCode; # exports geek_decode()

my @out = geek_decode(q(
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GB/C/CM/CS/CC/ED/H/IT/L/M/MU/P/SS/TW/AT d---x s+: a-- C++++ UB++++$
P++++$ L+ E--->+ W+++$ N++ !o K w--(++) O-- M-@ !V PS+++ PE Y+>++
PGP++ t+ 5? X+ R+++ !tv b++++ DI+++@ D++ G++++ e-(--) h* r++(+) z++*
------END GEEK CODE BLOCK------
)); # yes, thats the authors geek code

my ($key, $val);
print "[$key]n$valnn" while (($key, $val) = splice(@out, 0, 2));

Convert::GeekCode converts and generates Geek Code sequences (cf. http://geekcode.com/). It supports different langugage codes and user-customizable codesets.
Since version 0.5, this module uses YAML to represent the geek code tables, for greater readability and ease of deserialization. Please refer to http://www.yaml.org/ for more related information.

The geekgen and geekdec utilities are installed by default, and may be used to generate / decode geek code blocks, respectively

Pretty Code Web is a syntax highlighter for publishing code, written in any programming language, to the web.
Written in php it uses syntax files separate from the main code to highlight a specified language.
Main features:
- Syntax highlighting for (potentially) any language.
- User defined syntax files.
- User defined colors
- Separate colors for:
- 6 Keyword Groups
- Text Strings
- Operators
- Block and Line Comments
- Bracket Characters

IP::Country is a tool for fast lookup of country codes from IP addresses. Finding out the country of a client using only the IP address can be difficult.

Looking up the domain name associated with that address can provide some help, but many IP address are not reverse mapped to any useful domain, and the most common domain (.com) offers no help when looking for country.

IP::Country module comes bundled with a database of countries where various IP addresses have been assigned. Although the country of assignment will probably be the country associated with a large ISP rather than the client herself, this is probably good enough for most log analysis applications, and under test has proved to be as accurate as reverse-DNS and WHOIS lookup.

Code::Splice injects the contents of one subroutine at a specified point elsewhere.

SYNOPSIS

use Code::Splice;

Code::Splice::inject(
code => sub { print "fredn"; },
package => main,
method => foo,
precondition => sub {
my $op = shift;
my $line = shift;
$line =~ m/print/ and $line =~ m/four/;
},
postcondition => sub {
my $op = shift;
my $line = shift;
$line =~ m/print/ and $line =~ m/five/;
},
);

sub foo {
print "onen";
print "twon";
print "threen";
print "fourn";
print "fiven";
}

This module removes the contents of a subroutine (usually an anonymous subroutine created just for the purpose) and splices in into the program elsewhere.

Why, you ask?

Write stronger unit tests than the granularity of the API would otherwise allow

Write unit tests for nasty, interdependant speghetti code (my motivation -- hey, you gotta have tests before you can start refactoring, and if you cant write tests for the code, youre screwed)

Fix stupid bugs and remove stupid restrictions in other peoples code in a way thats more resiliant across upgrades than editing files you dont own

Be what "aspects" should be

Screw with your cow-orkers by introducing monster heisenbugs

Play with self-modifying code

Write self-replicating code (but be nice, were all friends here, right?)

The specifics:

The body of the code { } block are extracted from the subroutine and inserted in a place in the code specified by the call to the splice() function. Where the new code is spliced in, the old code is spliced out. The package and method arguments are required and tell the thing how to find the code to be modified. The code argument is required as it specifies the code to be spliced in. That same code block should not be used for anything else under penalty of coredump.

The rest of the argumets specify where the code is to be inserted. Any number of precondition and postcondition arguments provide callbacks to help locate the exact area to splice the code in at. Before the code can e spliced in, all of the precondition blocks must have returned true, and none of the postcondition blocks may have yet returned true. If a postcondition returns true before all of the precondition blocks have, an error is raised. Both blocks get called numerous times per line and get passed a reference to the B OP object currently under consideration and the text of the current line:

precondition => sub {
my $op = shift;
my $line = shift;
$line =~ m/print/ and $line =~ m/four/;
},
... or...
precondition => sub { my $op = shift; $op->name eq padsv and $op->sv->sv =~ m/fred/; },

Its possible to insert code in the middle of an expression when testing ops, but when testing the text of the line of code, the spliced in code will always replace the whole line.
Ill probably drop sending in the opcode in a future version, at least for the precondition/postcondition blocks, or maybe Ill swap them to the 2nd arg so theyre more optional.

Do not attempt to match text in comments as it wont be there. The code in $line is re-generated from the bytecode using B::Deparse and will vary from the original source code in a few ways, including changes to formatting, changes to some idioms and details of the expressions, and formatting of the code with regards to whitespace.

The splicing code will die if it fails for any reason. This will likely change in possible future versions.
There are also label and line arguments that create preconditions for you, for simple cases. Of course, you shouldnt use line for anything other than simple experimentation.

References to lexical variables in the code to be injected are replaced with references to the lexical variables of the same name in the location the code is inserted into. If a variable of the same name doesnt exist there, its an error. ... but it probably shouldnt be an error, at least in the cases where the code being spliced in declares that lexical with my, or when the variable was initiailized entirely outside of the sub block being spliced in and was merely closed over by it.

See the comments in the source code (at the top, in a nice block) for my todo/desired features. Let me know if there are any features in there or yet unsuggested that you want. I wont promise them, but I would like to hear about them.

MyDBO is a powerful object-oriented code generator for PHP/MySQL Web application developers.
It is designed to remove the hassle of implementing familiar database operations (select, update, insert, etc) over and over again when creating Web applications. MyDBO Code Generator creates code for accessing your database tables without you having to worry about connections or SQL queries.
It also allows you to approach your database in an object-oriented fashion, thus giving you real flexibility. It uses templates to generate code, so it is also possible to create your own templates.
Main features:
- Forget about accessing your database with SQL queries.
- Use the far more flexible object-oriented approach.
- Create logic foreign key links between your tables and navigate between your objects.
- Map the default MySQL date type to whatever you want.
- Create your own templates for unlimited possibilities.
- Fast and reliable.
- Should your database structure change, just re-generate the code.
- Easy to generate with the generation wizard.
- The generated code has standard comments for each class and functions.
- Free for personal and commercial use (GNU), Open source.
- Clean and tested code.
Enhancements:
- Boolean return values were added in API methods.
- A LIMIT argument was added in the tableCollector of the businessAPI plugin.
- The number of queries to execute when using Collector was reduced to 1.
- The use of database connections was optimized, and $DB is now a global variable.
- Memory is allowed increased to 16M.
- The ADOdb installation was customized to be minimal.
- instantAdmin was updated with a new API.
- Collector classes can now return the number of results only.

Bio::Tools::CodonTable is a bioperl codon table object.

SYNOPSIS

# This is a read-only class for all known codon tables. The IDs are
# the ones used by nucleotide sequence databases. All common IUPAC
# ambiguity codes for DNA, RNA and animo acids are recognized.

# to use
use Bio::Tools::CodonTable;

# defaults to ID 1 "Standard"
$myCodonTable = Bio::Tools::CodonTable->new();
$myCodonTable2 = Bio::Tools::CodonTable -> new ( -id => 3 );

# change codon table
$myCodonTable->id(5);

# examine codon table
print join ( , "The name of the codon table no.", $myCodonTable->id(4),
"is:", $myCodonTable->name(), "n");

# translate a codon
$aa = $myCodonTable->translate(ACU);
$aa = $myCodonTable->translate(act);
$aa = $myCodonTable->translate(ytr);

# reverse translate an amino acid
@codons = $myCodonTable->revtranslate(A);
@codons = $myCodonTable->revtranslate(Ser);
@codons = $myCodonTable->revtranslate(Glx);
@codons = $myCodonTable->revtranslate(cYS, rna);

#boolean tests
print "Is a startn" if $myCodonTable->is_start_codon(ATG);
print "Is a termianatorn" if $myCodonTable->is_ter_codon(tar);
print "Is a unknownn" if $myCodonTable->is_unknown_codon(JTG);

Codon tables are also called translation tables or genetics codes since that is what they try to represent. A bit more complete picture of the full complexity of codon usage in various taxonomic groups presented at the NCBI Genetic Codes Home page.

CodonTable is a BioPerl class that knows all current translation tables that are used by primary nucleotide sequence databases (GenBank, EMBL and DDBJ). It provides methods to output information about tables and relationships between codons and amino acids.

This class and its methods recognized all common IUPAC ambiguity codes for DNA, RNA and animo acids. The translation method follows the conventions in EMBL and TREMBL databases.
It is a nuisance to separate RNA and cDNA representations of nucleic acid transcripts. The CodonTable object accepts codons of both type as input and allows the user to set the mode for output when reverse translating. Its default for output is DNA.

Note: This class deals primarily with individual codons and amino acids. However in the interest of speed you can translate longer sequence, too. The full complexity of protein translation is tackled by Bio::PrimarySeqI::translate.

XML::Diff is a Perl module for XML DOM-Tree based Diff & Patch Module.

SYNOPSIS

my $diff = XML::Diff->new();

# to generate a diffgram of two XML files, use compare.
# $old and $new can be filepaths, XML as a string,
# XML::LibXML::Document or XML::LibXML::Element objects.
# The diffgram is a XML::LibXML::Document by default.
my $diffgram = $diff->compare(
-old => $old_xml,
-new => $new_xml,
);

# To patch an XML document, an patch. $old and $diffgram
# follow the same formatting rules as compare.
# The resulting XML is a XML::LibXML::Document by default.
my $patched = $diff->patch(
-old => $old,
-diffgram => $diffgram,
);

This module provides methods for generating and applying an XML diffgram of two related XML files. The basis of the algorithm is tree-wise comparison using the DOM model as provided by XML::LibXML.

The Diffgram is well-formed XML in the XVCS namespance and supports update, insert, delete and move operations. It is meant to be human and machine readable. It uses XPath expressions for locating the nodes to operate on.

PHP Active Code Library (ACL) is a PHP 5 class used to store and call PHP files that are stored in a database.

The files are stored in a plain text field and not a binary field. PHP ACL also takes care of include/require calls.

If a file includes another file stored in the database, PHP ACL takes care of getting, generating, and including that file.