Free code software for linux

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

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.

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.

Pretty Code Web is a syntax highlighter for publishing code, written in any programming language, to the web.
Written in php it uses syntax files separate from the main code to highlight a specified language.
Main features:
- Syntax highlighting for (potentially) any language.
- User defined syntax files.
- User defined colors
- Separate colors for:
- 6 Keyword Groups
- Text Strings
- Operators
- Block and Line Comments
- Bracket Characters

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.

Call Of Duty 2 Linux Multiplayer Server Code is a COD2 linux server.

!! IMPORTANT !!

Call of Duty 2 Linux Server is NOT SUPPORTED by Activision Customer Support. Please do not call with any questions related to this free beta product. There are other channels to aid you listed at the bottom of this document.

Introduction

This document explains how to install the Call of Duty 2 Linux server version 1.0. Installation from scratch and upgrading an existing installation are both covered.

Usage is very similar to Call of Duty and United Offensive... many of the console commands, command lines, and cvars are identical, so if you are comfortable maintaining dedicated servers for those games, you will find this process familiar.

MOD USERS: PLEASE READ...

It is recommended that any user modifications that have been installed to the Call of Duty 2 directory be removed before installing this package. These modifications are not supported by Activision and may not be compatible with some of the new features that are included. When installing or upgrading a server, if problems or unexpected behavior arise, your first step in troubleshooting should be to do a clean install with the original data files.

IF YOU HAVE A PROBLEM WITH "LIBSTDC++.SO.5" ...

(This is a frequent-enough problem to merit discussion in the introduction.)

If you are reading this, its probably because you tried to start your Linux server and saw this message:

./cod2_lnxded: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

COD2 is a C++ program built with gcc 3.3.4, which means it needs a system library specific to gcc 3.3. Older Linux systems wont have this installed, and were starting to see newer Linux distributions that dont have this either, since they are supplying an incompatible gcc 3.4 version. The good news is that you can drop the needed library into your system without breaking anything else.

Here is the library you need, if your Linux distribution doesnt supply it:

http://icculus.org/updates/cod/gcc3-libs.tar.bz2

You want to unpack that somewhere that the dynamic linker will see it (if you are sure it wont overwrite any files, you can even use /lib).

The brave can put it in the same directory as the game and run the server like this:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. ./cod2_lnxded

Now the server will start.

Upgrading from 1.0 to Linux 1.0a.

Just stop the game server, replace cod2_lnxded on your server with the version included in this package, and restart the game server. 1.0a is just a minor hotfix and requires no other code changes.

As the hotfix is Linux-specific there is no Windows version of 1.0a.

Installation From Scratch

- Get the retail Call of Duty 2 disc(s) (there may be multiple discs depending on what edition of the game you have obtained, or perhaps a single DVD-ROM disc).
- Copy the contents of disc ones "Setup/Data" directory to wherever you want to install the Call of Duty 2 Linux server. There should be a "localization.txt" file in the root of this directory, and a "Main" Subdirectory. Each additional disc should be opened and the contents of each "Data" folder should be copied over to the existing Main folder. When you have copied everything, the final installation size is around 3.5 gigabytes.
- Alternately, you may install on Windows and copy the installed game to your Linux system, but many will opt to skip this step since the data files are uncompressed and easily accessible on the discs. Final installation size is around 3.5 gigabytes.
- Unpack this archive in the root of the newly-copied tree, so "cod2_lnxded" is in the same directory as "localization.txt". Unlike the original Call of Duty, there are not seperate .so files like "game.mp.i386.so", so dont be concerned when you dont see them.
- Now, run the server:
cd /where/i/copied/callofduty2
./cod2_lnxded

- When you see "--- Common Initialization Complete ---", the game server has started, but you need to start a map before the server will accept connections. At this point, type:

map mp_leningrad

("mp_leningrad" being a given maps name).

- Now you should see your server in the in-game browser. You will now want to customize your server, but that is beyond the scope of this document.