Free coded software for linux

XML::Diff is a Perl module for XML DOM-Tree based Diff & Patch Module.

SYNOPSIS

my $diff = XML::Diff->new();

# to generate a diffgram of two XML files, use compare.
# $old and $new can be filepaths, XML as a string,
# XML::LibXML::Document or XML::LibXML::Element objects.
# The diffgram is a XML::LibXML::Document by default.
my $diffgram = $diff->compare(
-old => $old_xml,
-new => $new_xml,
);

# To patch an XML document, an patch. $old and $diffgram
# follow the same formatting rules as compare.
# The resulting XML is a XML::LibXML::Document by default.
my $patched = $diff->patch(
-old => $old,
-diffgram => $diffgram,
);

This module provides methods for generating and applying an XML diffgram of two related XML files. The basis of the algorithm is tree-wise comparison using the DOM model as provided by XML::LibXML.

The Diffgram is well-formed XML in the XVCS namespance and supports update, insert, delete and move operations. It is meant to be human and machine readable. It uses XPath expressions for locating the nodes to operate on.

Code::Splice injects the contents of one subroutine at a specified point elsewhere.

SYNOPSIS

use Code::Splice;

Code::Splice::inject(
code => sub { print "fredn"; },
package => main,
method => foo,
precondition => sub {
my $op = shift;
my $line = shift;
$line =~ m/print/ and $line =~ m/four/;
},
postcondition => sub {
my $op = shift;
my $line = shift;
$line =~ m/print/ and $line =~ m/five/;
},
);

sub foo {
print "onen";
print "twon";
print "threen";
print "fourn";
print "fiven";
}

This module removes the contents of a subroutine (usually an anonymous subroutine created just for the purpose) and splices in into the program elsewhere.

Why, you ask?

Write stronger unit tests than the granularity of the API would otherwise allow

Write unit tests for nasty, interdependant speghetti code (my motivation -- hey, you gotta have tests before you can start refactoring, and if you cant write tests for the code, youre screwed)

Fix stupid bugs and remove stupid restrictions in other peoples code in a way thats more resiliant across upgrades than editing files you dont own

Be what "aspects" should be

Screw with your cow-orkers by introducing monster heisenbugs

Play with self-modifying code

Write self-replicating code (but be nice, were all friends here, right?)

The specifics:

The body of the code { } block are extracted from the subroutine and inserted in a place in the code specified by the call to the splice() function. Where the new code is spliced in, the old code is spliced out. The package and method arguments are required and tell the thing how to find the code to be modified. The code argument is required as it specifies the code to be spliced in. That same code block should not be used for anything else under penalty of coredump.

The rest of the argumets specify where the code is to be inserted. Any number of precondition and postcondition arguments provide callbacks to help locate the exact area to splice the code in at. Before the code can e spliced in, all of the precondition blocks must have returned true, and none of the postcondition blocks may have yet returned true. If a postcondition returns true before all of the precondition blocks have, an error is raised. Both blocks get called numerous times per line and get passed a reference to the B OP object currently under consideration and the text of the current line:

precondition => sub {
my $op = shift;
my $line = shift;
$line =~ m/print/ and $line =~ m/four/;
},
... or...
precondition => sub { my $op = shift; $op->name eq padsv and $op->sv->sv =~ m/fred/; },

Its possible to insert code in the middle of an expression when testing ops, but when testing the text of the line of code, the spliced in code will always replace the whole line.
Ill probably drop sending in the opcode in a future version, at least for the precondition/postcondition blocks, or maybe Ill swap them to the 2nd arg so theyre more optional.

Do not attempt to match text in comments as it wont be there. The code in $line is re-generated from the bytecode using B::Deparse and will vary from the original source code in a few ways, including changes to formatting, changes to some idioms and details of the expressions, and formatting of the code with regards to whitespace.

The splicing code will die if it fails for any reason. This will likely change in possible future versions.
There are also label and line arguments that create preconditions for you, for simple cases. Of course, you shouldnt use line for anything other than simple experimentation.

References to lexical variables in the code to be injected are replaced with references to the lexical variables of the same name in the location the code is inserted into. If a variable of the same name doesnt exist there, its an error. ... but it probably shouldnt be an error, at least in the cases where the code being spliced in declares that lexical with my, or when the variable was initiailized entirely outside of the sub block being spliced in and was merely closed over by it.

See the comments in the source code (at the top, in a nice block) for my todo/desired features. Let me know if there are any features in there or yet unsuggested that you want. I wont promise them, but I would like to hear about them.

Code::Blocks is a free C++ IDE built specifically to meet the most demanding needs of its users. The Code::Blocks project was designed, right from the start, to be extensible and configurable.
Built around a plugin framework, Code::Blocks can be extended with plugin DLLs. It includes a plugin wizard so you can compile your own plugins! (Free SDK downloaded separately)
Main features:
- Open Source! GPL2, no hidden costs.
- Cross-platform. Runs on Linux or Windows (uses wxWidgets).
- Made in GNU C++. No interpreted languages or proprietary libs needed.
- Comes in two presentations: Standalone, and MinGW bundle
- Devpack support (optional)
- Extensible thru plugins (SDK available in the downloads section)
- Multiple compiler support:
- GCC (MingW / Linux GCC)
- MSVC++
- Digital Mars
- Borland C++ 5.5
- Open Watcom
- Compiles directly or with makefiles
- Predefined project templates
- Custom template support
- Uses XML format for project files.
- Multi-target projects
- Workspaces support
- Imports MSVC projects and workspaces (NOTE: assembly code and inter-project dependencies not supported yet)
- Imports Dev-C++ projects
- Integrates with GDB for debugging
- Syntax highlighting, customizable and extensible
- Code folding for C++ and XML files.
- Tabbed interface
- Code completion plugin
- Class Browser
- Smart indent
- One-key swap between .h and .c/.cpp files
- Open files list for quick switching between files (optional)
- External customizable "Tools"
- To-do list management with different users

HTML Code Convert helps speed up the conversion of HTML code into different format including Java Script, JavaServer Pages, Microsoft ASP, PHP, Perl, Python, and the UNIX Shell. It is particularly useful in CGI scripting.
Enhancements:
- Colors and font selected in prefeferences box.
- Fixe bug with Quit button. First try to support accessibility.
- Updated schemas.

Dekadent is an IRC bot coded in C. Some of Its features are: controlled user access, autoop, autovoice, shitlist, autojoin, different configurations per user and per channel and many other.
Well, first of all i have less than 9 months(first bot version) of real C knowledge and since the better way to learn C in real "life" is coding in C i decided to make a program that I can develop and develop and develop.... since i spend a lot of time using IRC I decided to code an IRC Bot... I decided to release it with many incomplete features because i want to fix the bugs that can appear and since Im not coding it on a regular basis. With this release I can maybe get a *wish* to code other features. Its important to receive feedback to continue to code it.
Main features:
- Ok its not a big big bot but for a first version it has many features.
- Many features have already been implemented and for more features in the future see TODO file.
- This version (0.9) has different user access, autoop, autovoice, shitlist, autojoin, joinmsg, different user/channel configuration, auto identify, plain text bot configuration, add/remove channels on the fly, create/erase users/channels on the fly even change channel options, ctcps answer, log stuff, web news etc etc. Total access levels configuration and many other things on include/defines.h. DCC Chat (partyline) support, news system...
- Many other features. This bot wont replace eggdrop features because eggdrop is a full fledged irc bot and its coded by experienced coders who have been working on it 10+- years while I only have some months of experience in C...
Enhancements:
- Bug fix on !join when bot send a message to sdata.target instead of partyline.
- Bug fix on !deluser, deleted user will now be cleared from memory.
- Bug fix on !reload and !rehash.
- Chaging web.c (!web dbot) to work with new dbots site.
- Minor changes

MyDBO is a powerful object-oriented code generator for PHP/MySQL Web application developers.
It is designed to remove the hassle of implementing familiar database operations (select, update, insert, etc) over and over again when creating Web applications. MyDBO Code Generator creates code for accessing your database tables without you having to worry about connections or SQL queries.
It also allows you to approach your database in an object-oriented fashion, thus giving you real flexibility. It uses templates to generate code, so it is also possible to create your own templates.
Main features:
- Forget about accessing your database with SQL queries.
- Use the far more flexible object-oriented approach.
- Create logic foreign key links between your tables and navigate between your objects.
- Map the default MySQL date type to whatever you want.
- Create your own templates for unlimited possibilities.
- Fast and reliable.
- Should your database structure change, just re-generate the code.
- Easy to generate with the generation wizard.
- The generated code has standard comments for each class and functions.
- Free for personal and commercial use (GNU), Open source.
- Clean and tested code.
Enhancements:
- Boolean return values were added in API methods.
- A LIMIT argument was added in the tableCollector of the businessAPI plugin.
- The number of queries to execute when using Collector was reduced to 1.
- The use of database connections was optimized, and $DB is now a global variable.
- Memory is allowed increased to 16M.
- The ADOdb installation was customized to be minimal.
- instantAdmin was updated with a new API.
- Collector classes can now return the number of results only.

PHP Active Code Library (ACL) is a PHP 5 class used to store and call PHP files that are stored in a database.

The files are stored in a plain text field and not a binary field. PHP ACL also takes care of include/require calls.

If a file includes another file stored in the database, PHP ACL takes care of getting, generating, and including that file.

This library defines set of data types and artithmetic operators, which can be used to code procedures with the intent to produce binary code which is difficult to analyse and reverse engineer.
This is achieved by moving all the calculations to yet another layer, which produces messy binary code being difficult to read and figure out, what calculations are actually performed and on which data.
Usage
The library provides arithmetic and logic operators to work with those data types. For example, addition performed in OBCODE would be coded as follows:
#include "obcode.h"
struct obyte ob1;
struct obyte ob2;
struct obyte obsum;
unsigned char sum;
obcode_init(0); /* Initialise obyte random */
obyte_set(&ob1, 12); /* Normal number 12 to obyte */
obyte_set(&ob2, 33); /* Normal number 33 to obyte */
obyte_add(&ob1, &ob2, &obsum); /* Perform OBCODE addition */
sum = obyte_get(&obsum); /* Return to normal world */
obcode_finish();
If those numbers were already encoded as obytes, people reverse engineering the code would never see 12 and 33, only messy operations on long, random looking data streams, eventually giving the product of 45.
Version restrictions:
- This library is still work in progress. It contains bugs and the operators set is very limited. Suggestions and improvements are welcome.
Enhancements:
- Code and documentation cleanups.