Main > Free Download Search >

Free suffix software for linux

suffix

Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 89
mod_suffix 20001002

mod_suffix 20001002


mod_suffix will grant access to files on the webserver based on their suffix. more>>
mod_suffix will grant access to files on the webserver based on their suffix.

If youre working on a large website and youre editing your files in place you might be confronted with a lot of backup files that various editors leave behind - like index.html~ (Emacs) or index.html.bak (UltraEdit).

This can be a problem if youre using server-side scripting languages like Embperl or PHP: Malicious users might try to open foobar.php.bak instead of foobar.php and peek at your code to see things they shouldnt see (like bad programming style or - even worse - the password to your database).

mod_suffix tries to solve this problem by blocking access to all files that do not end with a pre-defined suffix. This might seem paranoid but at least it is a rather fast and secure method. Also, it should be flexible enough for most cases.

<<less
Download (0.008MB)
Added: 2006-04-20 License: BSD License Price:
1283 downloads
Suffix tree implementation library 1.2

Suffix tree implementation library 1.2


Suffix tree implementation library is a C library, an implementation of the suffix trees algorithm to store/retrieve key/data pa more>>
Suffix tree implementation library is a C library, an implementation of the suffix trees algorithm to store/retrieve key/data pairs.
The main advantages are a linear indexing time, little memory usage, and very fast retrieving.
It has been developped on FreeBSD/gcc but should be fairly portable.
The source code "testsfx.c" show an example of how to use the library both for inserting, retrieving, and deleting data. There arent many functions and comments should be enough to give you an idea of how to use the library. (read the header of the source file)
You should edit sfxdisk.h to suit your needs: you can change the alphabet size and the offset type. It should be OK to use "long long" 64 bits ints instead of long, in fact I tested it succesfully but havent gone to the point of filling more than 2 GB of data (needless to say you need a 64 bits filesystem).
Two "tools" come with the library (new with version 1.2): dumpsfx and loadsfx. dumpsfx is used to dump the database: dumpsfx [-s separator] if you want to output the result as readable text or dumpsfx < file.sfx > -h to output it for reloading with loadsfx.
dumpsfx outputs on stdout and loadsfx reads from stdin. loadsfx < suffix tree file to create > < dumped_file
Enhancements:
- removed an useless offset incrementation in STwritenode
<<less
Download (0.015MB)
Added: 2006-08-07 License: GPL (GNU General Public License) Price:
1189 downloads
Eunit 1.1

Eunit 1.1


Eunit is an Erlang unit test suite. more>>
Eunit project is an Erlang test suite tool, inspired by agile development ideas.
Usage:
Launch example unit test with:
erl -config sys.config
and then
eunit:run([eunit_examples], {suffix, "_test"}).
Enhancements:
- This release is a complete rewrite.
- Writing unit tests should now be simpler than with the previous version.
- This release can also be used with the Aegis configuration management system for continuous integration.
<<less
Download (0.011MB)
Added: 2005-11-29 License: MPL (Mozilla Public License) Price:
1426 downloads
FuLFS 0.0.4

FuLFS 0.0.4


FuLFS is a simple hack to store and read very large files on/from a filesystem with small maximum file size. more>>
FuLFS is a simple hack to store and read very large files on/from a filesystem with small maximum file size. The primary purpose was putting DVD-size images on FAT32 and use it transparently. The files are stored in the form name.aa, name.ab, ...
Usage:
./fulfs physical-storage-dir virtual-dir [ chunk size ]
where the chunk size can be completed with a k/K/m/M/g/G suffix, meaning a
decimal or binary (upper case) factor of the particular unit.
Installation:
Install pkgconfig, install fuse library (version >>2.5.0, from http://fuse.sourceforge.net or a modern Linux distribution, including the development files (eg. libfuse-dev on Debian).
Run "make".
Enhancements:
- The file descriptor caching was fixed.
- Chunk set control was optimized.
- The unlink operation will return more reliable error codes now.
- The license was converted to the original BSD style.
<<less
Download (0.008MB)
Added: 2007-06-25 License: BSD License Price:
851 downloads
ExtSub 1.00

ExtSub 1.00


ExtSub is an utility which extracts and decodes subtitle data from VOB files. more>>
ExtSub is an utility which extracts and decodes subtitle data from VOB files. This program is for extracting subtitles from DVD VOB files. It does not descramble CSS-encrypted files. To compile simpy type "make". The command line parameters are as next:


infile= The VOB file from which to extract subtitles.

videofile= A file to which to write MPEG 2 video stream data.
(optional, highly experimental)

subname= The prefix of all subtitle files (see below for
details on the individual files).

convscript= An optional shell script, which will invoke
ImageMajicks "convert" utility to turn raw subtitle
image files into TIFF files.

id= The optional ID of the subtitle stream to be extracted
(default is 0). The specification allows IDs 0-31.

Each subtitle caption in the source file generates 3 output files with the suffixes ".gray", ".sub" and ".info".

The .gray file is a raw 8bpp bitmap image of the caption. DVD subtitles however are only 2bpp. in order to see anything with the naked eye using a program such as Imagemajicks "convert". it will probably be necessary to use the Enhance->Normalise function.

The .info file is a text file containing information about the caption, such as its resolution and and alpha channel data.

The .sub file is the raw data as extracted from the VOB source. Details of its syntax is available from http://sam.zoy.org/doc/dvd/subtitles/
<<less
Download (0.017MB)
Added: 2006-07-31 License: GPL (GNU General Public License) Price:
1183 downloads
SWISH++ 6.1.4

SWISH++ 6.1.4


SWISH++ is file indexing and searching engine typically used for web servers. more>>
SWISH++ is a Unix-based file indexing and searching engine (typically used to index and search files on web sites).
SWISH++ project was based on SWISH-E although SWISH++ is a complete rewrite. SWISH++ was developed to circumvent my difficulties with using the SWISH-E package.
SWISH++ has been ported to compile and run under Microsoft Windows by Robert J. Lebowitz and Christoph Conrad.
Main features:
- Lightning-fast indexing
- Indexes META elements, ALT, and other attributes
- Selectively not index text within HTML or XHTML elements
- Intelligently index mail and news files
- Index Unix manual page files
- Index LaTeX and RTF documents
- Index ID3 tags of MP3 files
- Index non-text files such as Microsoft Office documents
- Apply filters to files on-the-fly prior to indexing
- Modular indexing architecture
- Index new files incrementally
- Index remote web sites
- Handles large collections of files
- Lightning-fast searching
- Optional word stemming (suffix stripping)
- Ability to run as a search server
- Easy-to-parse results format
- XML results format
- Generously commented source code
Enhancements:
- Indexing of some ID3 tags was broken.
<<less
Download (0.29MB)
Added: 2006-03-15 License: GPL (GNU General Public License) Price:
1318 downloads
Algorithm::Huffman 0.09

Algorithm::Huffman 0.09


Algorithm::Huffman is a Perl extension that implements the Huffman algorithm. more>>
Algorithm::Huffman is a Perl extension that implements the Huffman algorithm.

SYNOPSIS

use Algorithm::Huffman;

my %char_counting = map {$_ => int rand(100)} (a .. z, A .. Z);
# or better the real counting for your characters
# as the huffman algorithm doesnt work good with random data :-))

my $huff = Algorithm::Huffman->new(%char_counting);
my $encode_hash = $huff->encode_hash;
my $decode_hash = $huff->decode_hash;

my $encode_of_hello = $huff->encode_bitstring("Hello");

print "Look at the encoding bitstring of Hello: $encode_of_hellon";
print "The decoding of $encode_of_hello is ", $huff->decode_bitstring($encode_of_hello), "";

This modules implements the huffman algorithm. The aim is to create a good coding scheme for a given list of different characters (or even strings) and their occurence numbers.

ALGORITHM

Please have a look to a good data compression book for a detailed view. However, the algorithm is like every good algorithm very easy.

Assume we have a heap (keys are the characters/strings; values are their occurencies). In each step of the algorithm, the two rarest characters are looked at. Both get a suffix (one "0", the other "1"). They are joined together and will occur from that time as one "element" in the heap with their summed occurencies. The joining creates a tree growing on while the heap is reducing.
Lets take an example. Given are the characters and occurencies.

a (15) b(7) c(6) d(6) e(5)

In the first step e and d are the rarest characters, so we create this new heap and tree structure:

a(15) de(11) b(7) c(6)

de
/
"0"/ "1"
d e

Next Step:

a(15) bc(13) de(11)

de bc
/ /
"0"/ "1" "0"/ "1"
d e b c

Next Step:

a(15) bcde(24)

bcde
/
"0"/ "1"
/
de bc
/ /
"0"/ "1" "0"/ "1"
d e b c

Next Step unifies the rest:

Huffman-Table
/
"0"/ "1"
/
/
bcde a
/
"0"/ "1"
/
de bc
/ /
"0"/ "1" "0"/ "1"
d e b c

Finally this encoding table would be created:

a 1
b 010
c 011
d 000
e 001

Please note, that there is no rule defining what element in the tree is ordered to left or to right. So its also possible to get e.g. the coding scheme:

a 0
b 100
c 101
d 110
e 111

<<less
Download (0.008MB)
Added: 2007-07-12 License: Perl Artistic License Price:
837 downloads
Samba::LDAP::Config 0.03

Samba::LDAP::Config 0.03


Samba::LDAP::Config is a Perl module to config file related tasks for Samba::LDAP. more>>
Samba::LDAP::Config is a Perl module to config file related tasks for Samba::LDAP.

SYNOPSIS

use Samba::LDAP::Config;

my $config = Samba::LDAP::Config->new()
or die "Cant create objectn";

# Returns where smbldap.conf, smbldap_bind.conf and
# smb.conf are located
my $smbldap_conf = $config->find_smbldap();
my $smbldap_bind_conf = $config->find_smbldap_bind();
my $samba_conf = $config->find_samba();

Various methods to find where the related Samba configuration files are saved, read them in and write them out etc. Subclasses Config::Tiny.

INTERFACE

new

Create a new Samba::LDAP::Config object

find_smbldap

Searches in usual places for smbldap.conf and returns location found.

my $smbldap_conf = $config->find_smbldap();

Returns the smbldap.conf in the scripts, if nothing found.

find_smbldap_bind

Searches in usual places for smbldap_bind.conf and returns location found.

my $smbldap_bind_conf = $config->find_smbldap_bind();

Returns the smbldap_bind.conf in the scripts, if nothing found.

find_samba

Searches in usual places for smb.conf and returns location found.

my $smb_conf = $config->find_samba();

Returns the smb.conf in the scripts, if nothing found.

read_conf

Wrapper to provide an instant error message as returned by the native Config::Tiny read method

my $conf = $config->read_conf( $filename );

read_string

Overrides Config::Tinys read_string to exclude the " " marks found in smbldap.conf and smbldap_bind.conf and remove section handling, as we dont have any [sections] in either of these files.

Also substitutes the suffix hash ( ${suffix} ) with its value.
Need to fix the smb.conf reading. Will use File::Samba or Config::Auto for it instead.

<<less
Download (0.080MB)
Added: 2007-01-12 License: Perl Artistic License Price:
1021 downloads
PDL::Audio 1.1

PDL::Audio 1.1


PDL::Audio is a Perl module for some PDL functions intended for audio processing. more>>
PDL::Audio is a Perl module for some PDL functions intended for audio processing.

SYNOPSIS

use PDL;
use PDL::Audio;

Oh well. Not much "introductory documentation" has been written yet.

NOTATION

Brackets around parameters indicate that the respective parameter is optional and will be replaced with some default value when absent (or undef, which might be different in other packages).

The sampling frequency and duration are by default (see individual descriptions) given in cycles/sample (or samples in case of a duration). That means if you want to specify a duration of two seconds, you have to multiply by the sampling frequency in HZ, and if you want to specify a frequency of 440 Hz, you have to divide by the sampling frequency:

# Syntax: gen_oscil duration*, frequency/
$signal = gen_oscil 2*HZ, 440/HZ;
# with a sampling frequency of 44100 Hertz:
$signal = gen_oscil 2*44100, 440/44100;

To help you, the required unit is given as a type suffix in the parameter name. A "/" means that you have to divide by the sampling frequency (to convert from Hertz) and a suffix of "*" indicates that a multiplication is required.
Most parameters named "size", "duration" (or marked with "*") can be replaced by a piddle, which is then used to give length and from (mono/stereo).

HEADER ATTRIBUTES

The following header attributes are stored and evaluated by most functions. PDL::Audio provides mutator methods for all them (e.g.

print "samplerate is ", $pdl->rate;
$pdl->comment("set the comment to this string");
rate

The sampling rate in hz.
filetype

The filetype (wav, au etc..). Must be one of:

FILE_NEXT FILE_AIFC FILE_RIFF FILE_BICSF FILE_NIST FILE_INRS FILE_ESPS
FILE_SVX FILE_VOC FILE_SNDT FILE_RAW FILE_SMP FILE_SD2 FILE_AVR
FILE_IRCAM FILE_SD1 FILE_SPPACK FILE_MUS10 FILE_HCOM FILE_PSION
FILE_MAUD FILE_IEEE FILE_DESKMATE FILE_DESKMATE_2500 FILE_MATLAB
FILE_ADC FILE_SOUNDEDIT FILE_SOUNDEDIT_16 FILE_DVSM FILE_MIDI
FILE_ESIGNAL FILE_SOUNDFONT FILE_GRAVIS FILE_COMDISCO FILE_GOLDWAVE
FILE_SRFS FILE_MIDI_SAMPLE_DUMP FILE_DIAMONDWARE FILE_REALAUDIO
FILE_ADF FILE_SBSTUDIOII FILE_DELUSION FILE_FARANDOLE FILE_SAMPLE_DUMP
FILE_ULTRATRACKER FILE_YAMAHA_SY85 FILE_YAMAHA_TX16 FILE_DIGIPLAYER
FILE_COVOX FILE_SPL FILE_AVI FILE_OMF FILE_QUICKTIME FILE_ASF
FILE_YAMAHA_SY99 FILE_KURZWEIL_2000 FILE_AIFF FILE_AU
path

The filename (or file specification) used to load or save a file.
format

Specifies the type the underlying file format uses. The samples will always be in short or long signed format.

Must be one of

FORMAT_NO_SND FORMAT_16_LINEAR FORMAT_8_MULAW FORMAT_8_LINEAR
FORMAT_32_FLOAT FORMAT_32_LINEAR FORMAT_8_ALAW FORMAT_8_UNSIGNED
FORMAT_24_LINEAR FORMAT_64_DOUBLE FORMAT_16_LINEAR_LITTLE_ENDIAN
FORMAT_32_LINEAR_LITTLE_ENDIAN FORMAT_32_FLOAT_LITTLE_ENDIAN
FORMAT_64_DOUBLE_LITTLE_ENDIAN FORMAT_16_UNSIGNED
FORMAT_16_UNSIGNED_LITTLE_ENDIAN FORMAT_24_LINEAR_LITTLE_ENDIAN
FORMAT_32_VAX_FLOAT FORMAT_12_LINEAR FORMAT_12_LINEAR_LITTLE_ENDIAN
FORMAT_12_UNSIGNED FORMAT_12_UNSIGNED_LITTLE_ENDIAN COMPATIBLE_FORMAT

PDL::Audio conviniently defines the following aliases for the following constants, that are already correct for the host byteorder:

FORMAT_ULAW_BYTE FORMAT_ALAW_BYTE FORMAT_LINEAR_BYTE
FORMAT_LINEAR_SHORT FORMAT_LINEAR_USHORT FORMAT_LINEAR_LONG
FORMAT_LINEAR_FLOAT FORMAT_LINEAR_DOUBLE
comment

The file comment (if any). device

The device to output audio. One of:

DEV_DEFAULT DEV_READ_WRITE DEV_ADAT_IN DEV_AES_IN DEV_LINE_OUT
DEV_LINE_IN DEV_MICROPHONE DEV_SPEAKERS DEV_DIGITAL_IN DEV_DIGITAL_OUT
DEV_DAC_OUT DEV_ADAT_OUT DEV_AES_OUT DEV_DAC_FILTER DEV_MIXER
DEV_LINE1 DEV_LINE2 DEV_LINE3 DEV_AUX_INPUT DEV_CD_IN DEV_AUX_OUTPUT
DEV_SPDIF_IN DEV_SPDIF_OUT

<<less
Download (0.25MB)
Added: 2006-06-19 License: Perl Artistic License Price:
1223 downloads
Autodist 1.3.2

Autodist 1.3.2


Autodist provides a source distribution management system. more>>
Autodist provides a source distribution management system.
Autodist is a source distribution management system that allows powerful mechanisms to define what is included in and excluded from a distribution and what license is used.
It is especially targeted at large software projects that create multiple distributions from a source tree.
Autodist supports distribution management in directory, file, and file content level, and automatic relicensing of a distribution.
The Autodist creates Makefile.am files from Makefile.ad files and configure.ac file from one or more configure.ad files. Any other file ending with .ad suffix will also be processed. The processed file will have the .ad suffix removed (see Preparing source tree). Autodist also creates and packages the distribution using common GNU distribution creation process, specificly `make dist.
Autodist, however, controls this process and during packaging phase the Autodist processes all files in the distribution (other than *.ad files, which has already been processed earlier by Autodist). The resulted package is a processed source distribution package, processed according to the rules specified in the distribution file(s) (see Creating distribution).
Any file in the source tree may use distdefs (distribution defines (see Distdefines)) which are defined in the distributions. When distribution is packaged only the files, directories and file content that is either outside of any distdef, or inside the defined distdefs will be included in the distribution. Any other file, directory or content in the file will be removed.
It is guaranteed, if a file, a directory or a piece of file content is not inside a defined distdef it will not be delivered to the distribution.
Any file, Makefile.am, configure.ac, or source file processed with Autodist is always compliant with the tools needed to process them. All files can also be processed with the corresponding tools even before processing them with Autodist. This makes it possible, for example, to compile sources before they have been processed, and undefined lines are removed. The distdefs are respected in source files by the preprocessor.
Autodist is not a binary packaging system. It is specificly used to create source distributions. A binary packaging system, however can be hooked to the distribution creation process, if needed.
Enhancements:
- The prereq directive was added.
- Support for extra user parameters for autodist hook scripts was added.
<<less
Download (0.21MB)
Added: 2007-06-01 License: BSD License Price:
875 downloads
Kukkaisvoima 7

Kukkaisvoima 7


Kukkaisvoima is a lightweight weblog system licensed under GNU GPL version 2. more>>
Kukkaisvoima is a lightweight weblog system licensed under GNU GPL version 2. The project is made with Python programming language.
It stores all blog entries as plain text files so you can easily write and edit those with your favorite editor. Motivation for Kukkaisvoima was to do simple everything in one package weblog with Python.
Main features:
- Multiple categories for one entry
- No external dependencies outside Pythons standard library (no need for database engine etc.)
- Comments
- RSS feed for all entries and for every category
Install instructions:
After downloading the latest version of Kukkaisvoima. Move the package to your webdirectory and do the following steps:
tar xvfz kukkaisvoima-(versionnumber).tar.gz
cd kukkaisvoima-(versionnumber)
chmod +x index.cgi
mkdir temp
You may need to modify the index.cgi script suffix (change .cgi to .py) or use different permissions for the index.cgi script or for the temp directory. Temp directory should be writable by the script. For more information and help consult your webserver manual or local Python/Unix guru.
Configuring and using:
Edit the Config variables found in kukkaisvoima_settings.py. After configuring you can write blog entries as html formatted text files in directory specified in config file. Kukkaisvoima will generate the blog from these entries. Every entry must be in the format of
nameoftheantry:YYYY-MM-DD:category1,category2.txt
For example:
helloworld:2006-12-28:general.txt
As seen in the example entry can have multiple categories separeted with comma.
Enhancements:
- This release introduced a spam question to prevent spam comments and an admin interface for deleting comments.
<<less
Download (0.016MB)
Added: 2007-04-26 License: GPL (GNU General Public License) Price:
911 downloads
makeself 2.1.4

makeself 2.1.4


makeself is a script to create self-extractable compressed tar archives. more>>
makeself.sh is a small shell script that generates a self-extractable tar.gz archive from a directory. The resulting file appears as a shell script (many of those have a .run suffix), and can be launched as is.
The archive will then uncompress itself to a temporary directory and an optional arbitrary command will be executed (for example an installation script). This is pretty similar to archives generated with WinZip Self-Extractor in the Windows world. Makeself archives also include checksums for integrity self-validation (CRC and/or MD5 checksums).
The makeself.sh script itself is used only to create the archives from a directory of files. The resultant archive is actually a compressed (using gzip, bzip2, or compress) TAR archive, with a small shell script stub at the beginning.
This small stub performs all the steps of extracting the files, running the embedded command, and removing the temporary files when its all over. All what the user has to do to install the software contained in such an archive is to "run" the archive, i.e sh nice-software.run.
I recommend using the "run" (which was introduced by some Makeself archives released by Loki Software) or "sh" suffix for such archives not to confuse the users, since they know its actually shell scripts (with quite a lot of binary data attached to it though!).
Usage
The syntax of makeself is the following:
makeself.sh [args] archive_dir file_name label startup_script [script_args]
args are optional options for Makeself. The available ones are :
--version : Prints the version number on stdout, then exits immediately
--gzip : Use gzip for compression (is the default on platforms on which gzip is commonly available, like Linux)
--bzip2 : Use bzip2 instead of gzip for better compression. The bzip2 command must be available in the command path. I recommend that you set the prefix to something like .bz2.run for the archive, so that potential users know that theyll need bzip2 to extract it.
--compress : Use the UNIX "compress" command to compress the data. This should be the default on all platforms that dont have gzip available.
--nocomp : Do not use any compression for the archive, which will then be an uncompressed TAR.
--notemp : The generated archive will not extract the files to a temporary directory, but in a new directory created in the current directory. This is better to distribute software packages that may extract and compile by themselves (i.e. launch the compilation through the embedded script).
--current : Files will be extracted to the current directory, instead of in a subdirectory. This option implies --notemp above.
--follow : Follow the symbolic links inside of the archive directory, i.e. store the files that are being pointed to instead of the links themselves.
--append (new in 2.1.x): Append data to an existing archive, instead of creating a new one. In this mode, the settings from the original archive are reused (compression type, label, embedded script), and thus dont need to be specified again on the command line.
--header : Makeself 2.0 uses a separate file to store the header stub, called "makeself-header.sh". By default, it is assumed that it is stored in the same location as makeself.sh. This option can be used to specify its actual location if it is stored someplace else.
--copy : Upon extraction, the archive will first extract itself to a temporary directory. The main application of this is to allow self-contained installers stored in a Makeself archive on a CD, when the installer program will later need to unmount the CD and allow a new one to be inserted. This prevents "Filesystem busy" errors for installers that span multiple CDs.
--nox11 : Disable the automatic spawning of a new terminal in X11.
--nowait : When executed from a new X11 terminal, disable the user prompt at the end of the script execution.
--nomd5 and --nocrc : Disable the creation of a MD5 / CRC checksum for the archive. This speeds up the extraction process if integrity checking is not necessary.
--lsm file : Provide and LSM file to makeself, that will be embedded in the generated archive. LSM files are describing a software package in a way that is easily parseable. The LSM entry can then be later retrieved using the -lsm argument to the archive. An exemple of a LSM file is provided with Makeself.
archive_dir is the name of the directory that contains the files to be archived
file_name is the name of the archive to be created
label is an arbitrary text string describing the package. It will be displayed while extracting the files.
startup_script is the command to be executed from within the directory of extracted files. Thus, if you wish to execute a program contain in this directory, you must prefix your command with "./". For example, ./program will be fine. The script_args are additionnal arguments for this command.
Enhancements:
- Fixed --info output.
- Generate random directory name when extracting files to . to avoid problems.
- Better handling of errors with wrong permissions for the directory containing the files.
- Avoid some race conditions, Unset the $CDPATH variable to avoid problems if it is set. Better handling of dot files in the archive directory.
<<less
Download (0.035MB)
Added: 2005-06-03 License: GPL (GNU General Public License) Price:
1610 downloads
Ruby/DICT 0.9.3

Ruby/DICT 0.9.3


Ruby/DICT is an RFC 2229 compliant client-side library implementation of the DICT protocol. more>>
Ruby/DICT is an RFC 2229 compliant client-side library implementation of the DICT protocol, written in the Ruby programming language. Ruby/DICT library can be used to write clients that access dictionary definitions from a set of natural language dictionary databases. In the words of the RFC:

The DICT protocol is designed to provide access to multiple databases. Word definitions can be requested, the word index can be searched (using an easily extended set of algorithms), information about the server can be provided (e.g., which index search strategies are supported, or which databases are available), and information about a database can be provided (e.g., copyright, citation, or distribution information). Further, the DICT protocol has hooks that can be used to restrict access to some or all of the databases.

The archive also includes rdict, a dictionary client built on top of the Ruby/DICT library.

Here are some examples of its usage:

$ rdict -D

This will provide you with a list of databases you can query.

$ rdict -S

This will provide you with a list of strategies you can employ to match words.

$ rdict -m -s prefix foo

This shows you a list of all words that begin with foo in all of the databases.

$ rdict -m -s re ^(cu|ke)rb$

This shows you all the definitions relating to both curb and kerb from all the databases. The re strategy allows regular expression matching.

$ rdict -m -s suffix fix

This shows a list of all words that end in fix in all of the databases.

<<less
Download (0.047MB)
Added: 2006-04-18 License: GPL (GNU General Public License) Price:
1286 downloads
GNU Trueprint 5.3

GNU Trueprint 5.3


GNU Trueprint is a project which allows you to print source code. more>>
GNU Trueprint is a project which allows you to print source code.
Trueprint is a program for printing source code in a variety of languages (C is the best supported) and other text files to postscript printers.
It supports a wealth of options to support printing source code, such as diff-marking, line numbers, indentation levels, file and function indices, and many others.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
Enhancements:
- Trueprint now uses autoconf and automake (Paul Smith, and the book GNU Autoconf, Automake and Libtool by Gary V. Vaughan et al, published by New Riders).
- Mention of trueprint.uu removed from README (Othmar Pasteka).
- Suffix .pike added for pike programs (Othmar Pasteka).
- Added include of sys/types.h before sys/stat.h to support FreeBSD (Dmitry Sivachenko).
- README.mswin removed (John Morey).
- If there isnt an lp or lpr command on your system when you run configure, trueprint will now be built to send postscript output to stdout by default (Othmar Pasteka).
- Choice options like --landscape and --option were broken due to a serious bug in options.c (Paul Smith).
- Added Canon LBP 3260 (Bjorn Wingman).
- Added HP Laserjet 1100 (Peter Green).
- Fix for handling arithmetic<<less
Download (0.17MB)
Added: 2007-02-27 License: GPL (GNU General Public License) Price:
974 downloads
File::Remote 1.17

File::Remote 1.17


File::Remote is a Perl module to read/write/edit remote files transparently. more>>
File::Remote is a Perl module to read/write/edit remote files transparently.

SYNOPSIS

#
# Two ways to use File::Remote
#
# First, the function-based style. Here, we can use the
# special :replace tag to overload Perl builtins!
#
use File::Remote qw(:replace); # special :replace tag

# read from a remote file
open(REMOTE, "host:/remote/file") or die $!;
print while (< REMOTE >);
close(REMOTE);

# writing a local file still works!
open(LOCAL, ">>/local/file");
print LOCAL "This is a new line.n";
close(LOCAL);

mkdir("host:/remote/dir", 0755);
unlink("host:/remote/file");
unlink("/local/file"); # still works too!
symlink("host:/remote/src", "host:/remote/dest");

chown("root", "other", "host:/remote/dir/file");
chmod(0600, "host:/remote/dir/file");

#
# Next, the object-oriented style, if you dont want to
# mess with the builtins.
#
use File::Remote;
my $remote = new File::Remote;

# Standard filehandles
$remote->open(FILE, ">>host:/remote/file") or die $!;
print FILE "Heres a line thats added.n";
$remote->close(FILE);

# Create a new file and change its permissions
$remote->mkdir("host:/remote/dir");
$remote->touch("host:/remote/dir/file");

# Move files around
$remote->copy("/local/file", "host:/remote/file") or warn $!;
$remote->move("host:/remote/file", "/local/file");

# Read and write whole files
my @file = $remote->readfile("host:/remote/file");
$remote->writefile("/local/file", @file);

# Backup a file with a suffix
$remote->backup("host:/remote/oldfile", "save");

# Use secure connection methods
my $secure = new File::Remote (rsh => "/usr/local/bin/ssh",
rcp => "/usr/local/bin/scp");
$secure->unlink("/local/file");
$secure->rmdir("host:/remote/dir");

This module takes care of dealing with files regardless of whether theyre local or remote. It allows you to create and edit files without having to worry about their physical location on the network. If a file passed into a function is of the form host:/path/to/file, then File::Remote uses rsh/rcp (or ssh/scp, depending on how you configure it) to edit the file remotely. Otherwise, it assumes the file is local and passes calls directly through to Perls core functions.

The nice thing about this module is that you can use it for all your file calls, since it handles both remote and local files transparently. This means you dont have to put a whole bunch of checks for remote files in your code. Plus, if you use the function-oriented interface along with the :replace tag, you can actually redefine the Perl builtin file functions. This means that your existing Perl scripts can automatically handle remote files with no re-engineering(!).

<<less
Download (0.015MB)
Added: 2007-04-27 License: Perl Artistic License Price:
911 downloads
Secleted [ 0 ] software to compare
  • Page: 1 of 5
  • 1
  • 2
  • 3
  • 4
  • 5