Free insert description here software for linux

IA-32 Instructions Database is a description of all IA-32 instructions in the form of SQL source, specifying operands, arguments, prefixes, encoding details, and description.

This database information initially came from XI (http://verb.org.ua/xi/) project, which was generated using information from (unfortunately outdated) IA-32 Intel(r) Architecture Software Developers Manual 2002.

Current release is alpha, so your feedback and bug reports are highly appreciable!

How to Build

Basically, there is no much need to build ia-32-instrdb, as it is just an sql file. However, you can type `make and if you have sqlite properly installed, you will get sqlites ia32instrs.db file shortly.

Template::Recall is a "Reverse callback" templating system.



SYNOPSIS

use Template::Recall;

my $tr = Template::Recall->new( template_path => /path/to/template/sections );

my @prods = (
soda,sugary goodness,$.99,
energy drink,jittery goodness,$1.99,
green tea,wholesome goodness,$1.59
);

$tr->render(header);

# Load template into memory

$tr->preload(prodrow);

for (@prods)
{
my %h;
my @a = split(/,/, $_);

$h{product} = $a[0];
$h{description} = $a[1];
$h{price} = $a[2];

print $tr->render(prodrow, %h);
}

# Remove template from memory

$tr->unload(prodrows);

print $tr->render(footer);

Template::Recall works using what I call a "reverse callback" approach. A "callback" templating system (i.e. Mason, Apache::ASP) generally includes template markup and code in the same file. The template "calls" out to the code where needed. Template::Recall works in reverse. Rather than inserting code inside the template, the template remains separate, but broken into sections. The sections are called from within the code at the appropriate times.

Test::STDmaker is a Perl module to generate test scripts, demo scripts from a test description short hand.

SYNOPSIS

#######
# Procedural (subroutine) interface
#
use Test::STDmake qw(find_t_roots get_data perl_command);

@t_path = find_t_paths()
$date = get_date();
$myperl = perl_command();

#####
# Class interface
#
use Test::STDmaker

$std = new Test::STDmaker( @options ); # From File::Maker

$success = $std->check_db($std_pm);
@t_path = $std->find_t_paths()
$date = $std->get_date();
$myperl = $std->perl_command();

$std->tmake( @targets, %options );
$std->tmake( @targets );
$std->tmake( %options );

######
# Internal (Private) Methods
#
$success = $std->build($std_driver_class);
$success = $std->generate();
$success = $std->print($file_out);

The Test::STDmaker program module provides the following capabilities:
Automate Perl related programming needed to create a test script resulting in reduction of time and cost.

Translate a short hand Software Test Description (STD) file into a Perl test script that eventually makes use of the Test module.

Translate the sort hand STD data file into a Perl demo script that demonstrates the features of the the module under test.

Provide in the POD of a STD file information required by a Military/Federal Government Software Test Description (STD) document that may easily be index and accessed by automated Test software. ISO, British Military require most of the same information, US agencies such as the FAA. The difference is that ISO, British Military do not dictate detail format. US agencies such as FAA will generally tailor down the DOD required formats.

Thus, there is an extremely wide variation in the format of the same information among ISO certified comericial activities and militaries other than US. Once the information is in a POD, different translators may format nearly exactly as dictated by the end user, whether it is the US DOD, ISO certified commericial activity, British Military or whoever. By being able to provide the most demanding, which is usually US DOD, the capabilities are there for all the others.

The Test::STDmaker package relieves the designer and developer from the burden of filling out word processor boiler plate templates (whether run-off, Word, or vi), counting oks, providing documentation examples, tracing tests to test requirments, making sure it is in the proper corporate, ISO or military format, and other such extremely time consuming, boring, development support tasks. Instead the designers and developers need only to fill in a form using a test description short hand. The Test::STDmaker will take it from there and automatically and quickly generate the desired test scripts, demo scripts, and test description documents.

Look at the economics. It does not make economically sense to have expensive talent do this work. In does not even make economically sense to take a bright 16 year, at mimimum wage and have him manually count oks. Perl can count those oks much much cheaper and it is so easily to automated with Perl. And something like this were you are doing it year in and year out, the saving are enormous. To a program manager or contract officer, this is what programming and computers are all about, saving money and increasing productivity, not object oriented oriented programing, gotos or other such things.

The Test::STDmaker class package automates the generation of Software Test Descriptions (STD) Plain Old Documentation (POD), test scripts, demonstrations scripts and the execution of the generated test scripts and demonstration scripts. It will automatically insert the output from the demonstration script into the POD -headx Demonstration section of the file being tested.

htmloptim project reduces the size of an HTML file by removing unnecessary characters like spaces, tabs, line feeds, and blank lines.
Enhancements:
- added the -p option (remove trailing spaces and tabs)
- added skipping of more < pre > like tags: < listing > < plaintext > < xmp >
- added description of the script

Xplain2sql converts files from Xplain to SQL. xplain2sql supports a very large subset of Xplain, and it can convert from Xplain to Microsoft SQL Server, DB/2, Inprise InterBase, PostgreSQL, Oracle, MySQL, or ANSI-92 SQL.
It can also generate an XML description of the generated SQL. This XML description can be used to create low-level middle-tier code.
A Delphi/ADO XSLT style sheet is included. The C source code release should compile on any platform with an ANSI C compiler.
There are binary releases for FreeBSD, BeOS, Linux, and Windows 2000.
Xplain2sql supports a very large subset of Xplain already, and it is continually extended until full support is reached. Currently it can convert from Xplain to Microsoft SQL Server, Inprise InterBase, DB/2, PostgreSQL, Microsoft Access, and ANSI-92 SQL:
- Microsoft SQL Server support is very complete.
- Quite complete DB/2 support. Non literal inits are currently missing.
- InterBase support for init works only for literal inits (so attributes dont work). And because InterBase doesnt have the concept of temporary table, the extend and value only work for a single user.
- PostgreSQL is quite complete with the new PostgreSQL 7.3 release.
- Initial, but fairly complete Oracle support.
- Generates Microsoft Access data definition commands. However, it seems impossible to run an entire script against an Access database. Having to run each create table statement by hand is quite tedious.
- Generates good ANSI-92, however inits with non-literal values cannot be supported by ANSI-92 because it doesnt have the concept of before and after insert triggers.
Enhancements:
- Assert support was added.
- If-then-else is supported in init [default] statements for dialects that support triggers.