Free teklib 1.04 software for linux

TEKlib is a games operating system and cross-development SDK for games.

TEKlib is an open-source library and operating system effort under the terms of the free MIT software license. This project has a many of facets; it is a

virtual operating system that runs hosted on platforms such as Linux, Windows, BSD and MorphOS,
freestanding operating system on architectures such as the Playstation 2, where it runs on a thin layer of ROM calls,
middleware providing a constistent interface across all hosting environments,
component library in that it is not strictly limited to OS services,
development platform that comes with a cross-platform build system and documentation tools.

TEKlib was started around the year 1999 out of frustration from the ended lifecycle of the AmigaOS and the lack of a worthy successor for its most basic principle, excellence by simplicity. Today, TEKlib is a virtual operating system, distributed over a set of portable libraries. You can use it as your sole environment on the Playstation 2 (provided that you are hardcore enough); most people however will use it as a development platform under Linux or Windows.

By picking from its facilities, it can serve as

a games operating system and cross-development SDK for games and everything multimedia,
a hosting environment for libraries that depend on non-trivial features like plugins and threads, striving for portability and durability,
a virtual OS target as a backend for applications that would have to be ported to many individual hosts,
a toolkit to provide an extensible virtual filesystem,
an ubiquitous component architecture that allows plugins and their host to compile from the same source on all platforms,
a small and powerful replacement for standard C libraries in embedded applications.

TEKlib is both an architecture and component library. In short, it can be embedded into any kind of library and application, and conversely, any kind of library and application can be based on TEKlib.

Religion is a Perl module that can generate tracebacks and create and install die() and warn() handlers.

This is a second go at a module to simplify installing die() and warn() handlers, and to make such handlers easier to write and control.

For most people, this just means that if use use Religion; then youll get noticably better error reporting from warn() and die(). This is especially useful if you are using eval().

Religion provides four classes, WarnHandler, DieHandler, WarnPreHandler, and DiePreHandler, that when you construct them return closures that can be stored in variables that in turn get invoked by $SIG{__DIE__} and $SIG{__WARN__}. Note that if Religion is in use, you should not modify $SIG{__DIE__} or $SIG{__WARN__}, unless you are careful about invoking chaining to the old handler.

Religion also provides a TraceBack function, which is used by a DieHandler after you die() to give a better handle on the current scope of your situation, and provide information about where you were, which might influence where you want to go next, either returning back to where you were, or going on to the very last. [Sorry - Ed.]

See below for usage and examples.

USAGE

DieHandler SUB

Invoke like this:

$Die::Handler = new DieHandler sub {
#...
};

where #... contains your handler code. Your handler will receive the following arguments:

$message, $full_message, $level, $eval,
$iline, $ifile, $oline, $ofile, $oscope

$message is the message provided to die(). Note that the default addition of " at FILE line LINE.n" will have been stripped off if it was present. If you want to add such a message back on, feel free to do so with $iline and $ifile.

$full_message) is the message with a scope message added on if there was no newline at the end of $message. Currently, this is not the original message that die() tacked on, but something along the lines of " at line 3 of the eval at line 4 of Foo.pln".

$eval is non-zero if the die() was invoked inside an eval.

The rest of the arguments are explained in the source for Religion::TraceBack. Yes, I need to document these, but not just now, for they are a pain to explain.
Whenever you install a DieHandler, it will automatically store the current value of $Die::Handler so it can chain to it. If you want to install a handler only temporarily, use local().

If your handler returns data using return or by falling off the end, then the items returns will be used to fill back in the argument list, and the next handler in the chain, if any, will be invoked. Dont fall off the end if you dont want to change the error message.

If your handler exits using last, then no further handlers will be invoked, and the program will die immediatly.

If your handler exits using next, then the next handler in the chain will be invoked directly, without giving you a chance to change its arguments as you could if you used return.

If your handler invokes die(), then die() will proceed as if no handlers were installed. If you are inside an eval, then it will exit to the scope enclosing the eval, otherwise it will exit the program.

WarnHandler SUB

Invoke like this:

$Warn::Handler = new WarnHandler sub {
#...
};

For the rest of its explanation, see DieHandler, and subsitute warn() for die(). Note that once the last DieHandler completes (or last is invoked) then execution will return to the code that invoked warn().

DiePreHandler SUB

Invoke like this:

$Die::PreHandler = new DiePreHandler sub {
#...
};

This works identically to $Die::Handler, except that it forms a separate chain that is invoked before the DieHandler chain. Since you can use last to abort all the handlers and die immediately, or change the messages or scope details, this can be useful for modifying data that all future handlers will see, or to dispose of some messages from further handling.

This is even more useful in $Warn::PreHandler, since you can just throw away warnings that you know arent needed.

WarnPreHandler SUB

Invoke like this:

$Warn::PreHandler = new WarnPreHandler sub {
#...
};

This works identically to $Warn::Handler, except that it forms a separate chain that is invoked before the WarnHandler chain. Since you can use last to abort all the handlers and return to the program, or change the messages or scope details, this can be useful for modifying data that all future handlers will see, or to dispose of some messages.

This is very useful, since you can just throw away warnings that you know arent needed.

TLSWrap is a TLS/SSL FTP wrapper/proxy for UNIX and Windows, allowing you to use your favourite FTP client with any TLS/SSL-enabled FTP server.
Main features:
- Full encryption of both control and data connections (data encryption is optional, see README).
- Allows existing FTP clients to support Transport Layer Security/Secure Socket Layer.
it gives TLS/SSL support for existing ftp clients
- Works on both UNIX and Windows.
- One process handles all connections (non-blocking I/O).
- A helper process does hostname lookups so the main process is free for other work during slow lookups.
- Both C source and Windows executables for both 32-bit (x86) and 64-bit (x64: AMD64 and EM64T) systems are available.
- Proper support for X.509 certificates
Enhancements:
- This release fixes a bug that could cause crashes on some systems.
- TLSWTray has been upgraded to MFC 8.

Tkx::Tutorial Perl module contains a tutorial about how to use Tkx.

Tk is a toolkit that allows you to create applications with graphical interfaces for Windows, Mac OS X and X11. The Tk toolkit is native to the Tcl programming language, but its ease of use and cross-platform availability has made it the GUI toolkit of choice for many other dynamic languages as well.

Tkx is a Perl module that makes the Tk toolkit available to Perl programs. By loading the Tkx module Perl programs can create windows and fill them with text, images, buttons and other controls that make up the user interface of the application.

Hello World

Lets start with the mandatory exercise of creating an application that greats the world. Here we make the application window contain a single button which will shut down the application if clicked. The code to make this happen is:

use Tkx;

Tkx::button(".b",
-text => "Hello, world",
-command => sub { Tkx::destroy("."); },
);
Tkx::pack(".b");

Tkx::MainLoop()

Save this to a file called hello.pl and then run perl hello.pl to start up the application. A window with the text "Hello, world" should appear on your screen.
After the Tkx module has been loaded by the use Tkx statement the application will show an empty window called ".". We create a button with the name ".b" and tell the window to display the button with the call to Tkx::pack(). After the layout of the window has been set up we need to pass control back to Tk so that it can draw the window and invoke our callback if the button is clicked. This is achieved by the Tkx::MainLoop() call at the end. Clicking the button will invoke the subroutine registered with the -command option of the button. In this case the callback simply destroys the window, which in turn will terminate the application.

Public Fox cleans stuff after downloading.

Tired of cleaning stuff people download? Use this to limit file downloading.
Prevent browser changes.

Public Fox blocks users from downloading unwanted files.
Locks down Add-ons.
Locks down Preferences.
Locks down about:config
All with a central password.

Devel::Profile is a Perl module to tell me why my perl program runs so slowly.

SYNOPSIS

perl -d:Profile program.pl
less prof.out

The Devel::Profile package is a Perl code profiler. This will collect information on the execution time of a Perl script and of the subs in that script. This information can be used to determine which subroutines are using the most time and which subroutines are being called most often.
To profile a Perl script, run the perl interpreter with the -d debugging switch. The profiler uses the debugging hooks. So to profile script test.pl the following command should be used:

perl -d:Profile test.pl

When the script terminates (or periodicly while running, see ENVIRONMENT) the profiler will dump the profile information to a file called prof.out. This file is human-readable, no additional tool is required to read it.

Note: Statistics are kept per sub, not per line.

glastree application builds live backup trees, with branches for each day. Users directly browse the past to recover older documents or retrieve lost files. Hard links serve to compress out unchanged files, while modified ones are copied verbatim. A prune utility effects a constant, sliding window.