Resources are a way to specify information of interest to program or
packages.
Applications use resource files to specify and document the values of
quantities or attributes of interest.
Resources can be loaded from or saved to resource files. Methods are
provided to search, modify and create resources. Packages use resources to
hardwire in their code the default values for their attributes, along with
documentation for the attributes themselves.
Packages inherit resources when subclassed, and the resource names are
updated dynamically to reflect a class hierarchy.
Methods are provided for interactive resource inspection and editing.
This is a specialized POD viewer to extract embedded tests and code
examples from POD. It doesn't do much more than that. pod2test does the
useful work.
After creating a Pod::Tests object, you parse the POD by calling one of
the available parsing methods documented below. You can call parse as many
times as you'd like, all examples and tests found will stack up inside the
object.
Once extracted, the tests can be built into stand-alone testing code using
the build_tests() and build_examples() methods. However, it is recommended
that you first look at the pod2test program before embarking on this.
LRC - Perl interface for longitudinal redundancy check generation
The Longitudinal Redundancy Check (LRC) is a one byte character,
commonly used as a byte-field in data transmission over analog systems.
Most commonly, in STX-ETX bounded strings sent in financial protocols.
Following some previous experience with such protocols, I wrote
an LRC function in perl and later decided to re-write in C
for efficiency. The result is this module String::LRC,
which generates this aforementioned byte.
Commonly used in financial protocols as follows with ETX (ASCII 03)
appended to LRC sum and packets after the STX (ASCII 02), payload,
and ETX chars.
Test::Class provides a simple way of creating classes and
objects to test your code in an xUnit style.
Built using Test::Builder it is designing to work with
other Test::Builder based modules (Test::More,
Test::Differences, Test::Exception, etc.)
Note: This module will make more sense if you are already
familiar with the "standard" mechanisms for testing perl code.
Those unfamiliar with Test::Harness, Test::Simple, Test::More
and friends should go take a look at them now.
Note: This is an early release. Things may change. Be warned.
Main Features of Sun's SpecTcl 1.1
==================================
Easy to Learn: SpecTcl's drag & drop interface along with a
powerful toolbar and on-line help make it easy
to start building GUI applications.
Tcl and Java Support: SpecTcl generates both Tcl and Java code.
Platform Independent: SpecTcl runs on all major platforms:
Solaris, SunOS, Linux, Windows 95,
Windows NT Server 3.51, Windows NT Workstation 3.51,
MacOS, and Irix.
Constraint Based Alignment and resizing of widgets (buttons,
Geometry Manager: check boxes, etc.) is automatic. This makes
creating dynamic UIs and cross platform UIs a snap!
Project Center is GNUstep's graphical integrated development environment
(IDE). It helps you to create all different kinds of projects like
Applications, Tools, Libraries and Bundles.
Project Center allows you to easily add and remove, edit and search files;
writes the project makefiles accordingly and supports you in the actual
process of building and debugging your project.
Even the management of a big project keeps being easy as Project Center's
file browser lets you always have a well sorted and categorized overview
over all the files in your project.
LICENSE: GPL2 or later
attrs is an MIT-licensed Python package with class decorators
that ease the chores of implementing the most common attribute-related
object protocols:
>>> import attr
>>> @attr.s
... class C(object):
... x = attr.ib(default=42)
... y = attr.ib(default=attr.Factory(list))
>>> i = C(x=1, y=2)
(If you don't like the playful attr.s and attr.ib, you can also use their
no-nonsense aliases attr.attributes and attr.attr).
You just specify the attributes to work with and attrs gives you:
a nice human-readable __repr__,
a complete set of comparison methods,
an initializer,
and much more
without writing dull boilerplate code again and again.
bitstring is a pure Python module designed to help make the creation and
analysis of binary data as simple and natural as possible.
BitStrings can be constructed from integers (big and little endian), hex, octal,
binary, strings or files. They can be sliced, joined, reversed, inserted into,
overwritten, etc. with simple functions or slice notation. They can also be
read from, searched and replaced, and navigated in, similar to a file or stream.
bitstring is open source software, and has been released under the MIT licence.
Java-Readline is a port of GNU Readline for Java. Or, to be more
precise, it is a JNI-wrapper to Readline. It is distributed under the
LGPL.
You must call Readline.load(ReadlineLibrary lib); before using any
other methods. If you omit the call to the load()-method, the pure
Java fallback solution is used. Possible values for lib are:
ReadlineLibrary.PureJava
ReadlineLibrary.GnuReadline
ReadlineLibrary.Editline
ReadlineLibrary.Getline
Note that all programs using GnuReadline will fall under the GPL,
since Gnu-Readline is GPL software!
The core idea of libee is to provide a small but hopefully convenient
API layer above the CEE standard. However, CEE is not finished. At the
time of this writing, CEE is under heavy development and even some of
its core data structures (like the data dictionary and taxonomy) have
not been fully specified. So for the time being, libee should be
thought of as a useful library that helps you get your events
normalized. If you program cleanly to libee, chances are not bad that
only relatively little effort is required to move your app over to be
CEE compliant (once the standard is out).