Free proposition 8 software for linux

Darkbot is a very fast and small program written in C language which connects to IRC from an Unix or Windows operating system and automatically "talks" and responds to users questions.
Originally created by Jason Hamilton as an aid for help channels to answer repeated questions from its virtually unlimited database, it has became a very popular talking robot in a generic sense, being used all over IRC networks for different purposes and in 18 languages.
THe dfata can be dynamically added and changed but also can be changed offline, working in its database.
An extensive but easy-to-understand list of commands and features, including some channel operation functions and levels of protection, makes Darkbot a very flexible but somehow powerful and complex robot, with almost human conversations and reactions.
Enhancements:
- Removed an unneeded line in main.c, that was used to "hide" warnings on WIN32, which is a very bad idea.
- Changed check_dbtimers() so it ignores the CVS directory, which contains information for the CVS server. This fixes a situation that seems to have only presented itself in FreeBSD, where it thinks the CVS directory is a timer, and sends out random garble every few seconds.
- configure.ac and source/Makefile.am; very minor updates.
- Fixed randq, which I accidentally broke when adding the
- I switch. This also fixes some problems that turned upon FreeBSD.
- Fixed a warning that came up in permbans.c about mixing types when compiling on OS X. I changed %d on line 198 to %ud.
- configure now checks for clock_t.
- configure now automatically checks for snprintf, and uses a replacement if its not found.
- docs/INSTALL.txt is now INSTALL in the toplevel dir.
- Another thing for automake to stop complaining about.
- The original configure script is now located in the scripts directory, and is called "Setup".
- docs/contributors.txt is now called AUTHORS in the top level of the distribution. Another thing automake complains about. I also worked on the appearance of this file, hopefully it looks a little better now.
- README.txt in the toplevel is now called "README". Automake complains about this file also, if its not found.
- This file is now called ChangeLog, and has been moved to the toplevel distribution dir. The reason for this is that automake complains, if it cant find this file.
- configure now checks for the presence of windows.h, and defines WIN32, if its found. This removes the need to do "make win". Until I add the noconsole option again, you can run darkbot with no console by doing "./darkbot &" in your cygwin shell.
- The configure.ac file is not yet complete, and most of the definitions listed in config.h are not completely implemented into the code yet. If you have problems, please let me know, and these files will become completely implemented as demand is met.
- Included premade Makefiles and configure script.
- Added "make convertdb", which will compile the database conversion utility, which encrypts the passwords in your userlist.db file.
- I added a Makefile.am in the toplevel, and in the source directory. These files are used in conjunction with GNU Automake to produce a Makefile.
- Added Makefile.ams and configure.ac for autoconf/automake.

AutoSplit is a Perl module that can split a package for autoloading.

SYNOPSIS

autosplit($file, $dir, $keep, $check, $modtime);

autosplit_lib_modules(@modules);

This function will split up your program into files that the AutoLoader module can handle. It is used by both the standard perl libraries and by the MakeMaker utility, to automatically configure libraries for autoloading.

The autosplit interface splits the specified file into a hierarchy rooted at the directory $dir. It creates directories as needed to reflect class hierarchy, and creates the file autosplit.ix. This file acts as both forward declaration of all package routines, and as timestamp for the last update of the hierarchy.
The remaining three arguments to autosplit govern other options to the autosplitter.

$keep

If the third argument, $keep, is false, then any pre-existing *.al files in the autoload directory are removed if they are no longer part of the module (obsoleted functions). $keep defaults to 0.

$check

The fourth argument, $check, instructs autosplit to check the module currently being split to ensure that it includes a use specification for the AutoLoader module, and skips the module if AutoLoader is not detected. $check defaults to 1.

$modtime

Lastly, the $modtime argument specifies that autosplit is to check the modification time of the module against that of the autosplit.ix file, and only split the module if it is newer. $modtime defaults to 1.

Typical use of AutoSplit in the perl MakeMaker utility is via the command-line with:

perl -e use AutoSplit; autosplit($ARGV[0], $ARGV[1], 0, 1, 1)

Defined as a Make macro, it is invoked with file and directory arguments; autosplit will split the specified file into the specified directory and delete obsolete .al files, after checking first that the module does use the AutoLoader, and ensuring that the module is not already currently split in its current form (the modtime test).

The autosplit_lib_modules form is used in the building of perl. It takes as input a list of files (modules) that are assumed to reside in a directory lib relative to the current directory. Each file is sent to the autosplitter one at a time, to be split into the directory lib/auto.

In both usages of the autosplitter, only subroutines defined following the perl __END__ token are split out into separate files. Some routines may be placed prior to this marker to force their immediate loading and parsing.

Multiple packages

As of version 1.01 of the AutoSplit module it is possible to have multiple packages within a single file. Both of the following cases are supported:

package NAME;
__END__
sub AAA { ... }
package NAME::option1;
sub BBB { ... }
package NAME::option2;
sub BBB { ... }

package NAME;
__END__
sub AAA { ... }
sub NAME::option1::BBB { ... }
sub NAME::option2::BBB { ... }

PostgreSQL is a highly-scalable, SQL compliant, open source object-relational database management system. With more than 15 years of development history, it is quickly becoming the de facto database for enterprise level open source solutions.
PostgreSQL is an object-relational database management system (ORDBMS) based on POSTGRES, Version 4.2, developed at the University of California at Berkeley Computer Science Department. POSTGRES pioneered many concepts that only became available in some commercial database systems much later.
PostgreSQL is an open-source descendant of this original Berkeley code. PostgreSQL supports SQL92 and SQL99.
Main features:
- complex queries
- foreign keys
- triggers
- views
- transactional integrity
- multiversion concurrency control
Additionally, PostgreSQL can be extended by the user in many ways, for example by adding new:
- data types
- functions
- operators
- aggregate functions
- index methods
- procedural languages
And because of the liberal license, PostgreSQL can be used, modified, and distributed by everyone free of charge for any purpose, be it private, commercial, or academic.

FindBin is a Perl module that can locate directory of original perl script.

SYNOPSIS

use FindBin;
use lib "$FindBin::Bin/../lib";

or

use FindBin qw($Bin);
use lib "$Bin/../lib";

Locates the full path to the script bin directory to allow the use of paths relative to the bin directory.

This allows a user to setup a directory tree for some software with directories < root >/bin and < root >/lib, and then the above example will allow the use of modules in the lib directory without knowing where the software tree is installed.
If perl is invoked using the -e option or the perl script is read from STDIN then FindBin sets both $Bin and $RealBin to the current directory.

EXPORTABLE VARIABLES

$Bin - path to bin directory from where script was invoked
$Script - basename of script from which perl was invoked
$RealBin - $Bin with all links resolved
$RealScript - $Script with all links resolved

docbook2X is a software package that converts DocBook documents into the GNU Texinfo format and the traditional Unix man page format.
Notable features include table support for man pages, internationalization support, and easy customization of the output using XSLT. (Easy, because unlike other converters, the docbook2X stylesheets are written in a modular way, and the character escaping and whitespace issues with the man-page and Texinfo formats are encapsulated away from the user.)
Enhancements:
- Errors in the Man-XML and Texi-XML DTD were fixed. These DTDs are now used to validate the output coming out of the stylesheets, as part of automated testing. (Validation provides some assurance that the result of the conversions are correct.)
- Several rendering errors were fixed after they had been discovered through automated testing.
- Two HTML files in the docbook2X documentation were accidentally omitted in the last release. They have been added.
- The pure-XSLT-based man-page conversion now supports table markup. The implemented was copied from the one by Michael Smith in the DocBook XSL stylesheets. Many thanks!
- As requested by Daniel Leidert, the man-pages stylesheets now support the segmentedlist, segtitle and seg DocBook elements.
- As suggested by Matthias Kievermagel, docbook2X now supports the code element.

B::Deparse is a Perl compiler backend to produce perl code.

SYNOPSIS

perl -MO=Deparse[,-d][,-fFILE][,-p][,-q][,-l] [,-sLETTERS][,-xLEVEL] prog.pl

B::Deparse is a backend module for the Perl compiler that generates perl source code, based on the internal compiled structure that perl itself creates after parsing a program. The output of B::Deparse wont be exactly the same as the original source, since perl doesnt keep track of comments or whitespace, and there isnt a one-to-one correspondence between perls syntactical constructions and their compiled form, but it will often be close. When you use the -p option, the output also includes parentheses even when they are not required by precedence, which can make it easy to see if perl is parsing your expressions the way you intended.

While B::Deparse goes to some lengths to try to figure out what your original program was doing, some parts of the language can still trip it up; it still fails even on some parts of Perls own test suite. If you encounter a failure other than the most common ones described in the BUGS section below, you can help contribute to B::Deparses ongoing development by submitting a bug report with a small example.

OPTIONS

As with all compiler backend options, these must follow directly after the -MO=Deparse, separated by a comma but not any white space.

-d

Output data values (when they appear as constants) using Data::Dumper. Without this option, B::Deparse will use some simple routines of its own for the same purpose. Currently, Data::Dumper is better for some kinds of data (such as complex structures with sharing and self-reference) while the built-in routines are better for others (such as odd floating-point values).

-fFILE

Normally, B::Deparse deparses the main code of a program, and all the subs defined in the same file. To include subs defined in other files, pass the -f option with the filename. You can pass the -f option several times, to include more than one secondary file. (Most of the time you dont want to use it at all.) You can also use this option to include subs which are defined in the scope of a #line directive with two parameters.

-l

Add #line declarations to the output based on the line and file locations of the original code.

-p

Print extra parentheses. Without this option, B::Deparse includes parentheses in its output only when they are needed, based on the structure of your program. With -p, it uses parentheses (almost) whenever they would be legal. This can be useful if you are used to LISP, or if you want to see how perl parses your input. If you say

if ($var & 0x7f == 65) {print "Gimme an A!"}
print ($which ? $a : $b), "n";
$name = $ENV{USER} or "Bob";
B::Deparse,-p will print
if (($var & 0)) {
print(Gimme an A!)
};
(print(($which ? $a : $b)), ???);
(($name = $ENV{USER}) or ???)

which probably isnt what you intended (the ??? is a sign that perl optimized away a constant value).

-P

Disable prototype checking. With this option, all function calls are deparsed as if no prototype was defined for them. In other words,

perl -MO=Deparse,-P -e sub foo (@) { 1 } foo @x

will print

sub foo (@) {
1;
}
&foo(@x);

making clear how the parameters are actually passed to foo.

-q

Expand double-quoted strings into the corresponding combinations of concatenation, uc, ucfirst, lc, lcfirst, quotemeta, and join. For instance, print

print "Hello, $world, @ladies, u$gentlemenE, uL$me!";

as

print Hello, . $world . , . join($", @ladies) . ,
. ucfirst($gentlemen) . , . ucfirst(lc $me . !);

Note that the expanded form represents the way perl handles such constructions internally -- this option actually turns off the reverse translation that B::Deparse usually does. On the other hand, note that $x = "$y" is not the same as $x = $y: the former makes the value of $y into a string before doing the assignment.

-sLETTERS

Tweak the style of B::Deparses output. The letters should follow directly after the s, with no space or punctuation. The following options are available:

C

Cuddle elsif, else, and continue blocks. For example, print

if (...) {
...
} else {
...
}
instead of
if (...) {
...
}
else {
...
}

The default is not to cuddle.

iNUMBER

Indent lines by multiples of NUMBER columns. The default is 4 columns.

T

Use tabs for each 8 columns of indent. The default is to use only spaces. For instance, if the style options are -si4T, a line thats indented 3 times will be preceded by one tab and four spaces; if the options were -si8T, the same line would be preceded by three tabs.

vSTRING.

Print STRING for the value of a constant that cant be determined because it was optimized away (mnemonic: this happens when a constant is used in void context). The end of the string is marked by a period. The string should be a valid perl expression, generally a constant. Note that unless its a number, it probably needs to be quoted, and on a command line quotes need to be protected from the shell. Some conventional values include 0, 1, 42, , foo, and Useless use of constant omitted (which may need to be -sv"Useless use of constant omitted." or something similar depending on your shell). The default is ???. If youre using B::Deparse on a module or other file thats required, you shouldnt use a value that evaluates to false, since the customary true constant at the end of a module will be in void context when the file is compiled as a main program.

-xLEVEL

Expand conventional syntax constructions into equivalent ones that expose their internal operation. LEVEL should be a digit, with higher values meaning more expansion. As with -q, this actually involves turning off special cases in B::Deparses normal operations.

If LEVEL is at least 3, for loops will be translated into equivalent while loops with continue blocks; for instance

for ($i = 0; $i < 10; ++$i) {
print $i;
}
turns into
$i = 0;
while ($i < 10) {
print $i;
} continue {
++$i
}

Note that in a few cases this translation cant be perfectly carried back into the source code -- if the loops initializer declares a my variable, for instance, it wont have the correct scope outside of the loop.

If LEVEL is at least 5, use declarations will be translated into BEGIN blocks containing calls to require and import; for instance,

use strict refs;
turns into
sub BEGIN {
require strict;
do {
strict->import(refs)
};
}
If LEVEL is at least 7, if statements will be translated into equivalent expressions using &&, ?: and do {}; for instance
print hi if $nice;
if ($nice) {
print hi;
}
if ($nice) {
print hi;
} else {
print bye;
}
turns into
$nice and print hi;
$nice and do { print hi };
$nice ? do { print hi } : do { print bye };

Long sequences of elsifs will turn into nested ternary operators, which B::Deparse doesnt know how to indent nicely.

Comix is a flat style for KDE 3.2+.
I hope this adds a little more fun to your desktop.
Thanks to all the authors of previous styles published for KDE. Please read AUTHORS, README and TODO.
Use the styles configuration button to overwrite the contour drawing color.
Use KDEs ControlCenter "Colors" dialog to adjust buttons- and highlight-color as well as the contrast.
Use kcontrols window decoration config-dialog to adjust title alignment and border width.
Also check the corresponding cursor theme at: http://www.kde-look.org/content/show.php?content=32627
Enhancements:
- kwin: title update fix
- kwin: window shading fix (Debian bug report 364459)
- kwin: inactive sunken buttons