Free epic software for linux

EPIC is a Perl IDE based on the Eclipse platform.
Features supported are syntax highlighting, on-the-fly syntax checking, content assistance, Perldoc support, a source formatter, templating support, and a Perl debugger.
A regular expression plugin and support for the eSpell spellchecker are also available.
Enhancements:
- The "testing" version 0.6.13 of EPIC is made available in the SourceForge download area, superseding the previously offered "stable" version 0.5.33. It contains mostly enhancements and fixes in the debugger, some of which cannot be provided in the "stable" version due to major differences in the code bases. The released version 0.6.13, which requires at least Eclipse 3.2, is not declared "stable" yet in order to maintain compatibility with Eclipse 3.1 in the "stable" branch.

EPIC4 is a new direction in ircII development. No longer is EPIC 100% backwards compatable with ircII, but instead we have chosen to find those things where compatability is undesirable, and fix them.
No gratuitous incompatabilities have been added, but lots of new code has been added to make EPIC the best ircII client we could make.
EPIC4 is derived directly from EPIC3, which was itself derived from IRC-II which is currently maintained by Matthew Green, and includes in whole all the additions included in the "plus" clients by Jeremy Nelson and all of the modifications in the "mod" clients by Jake Khuon.
EPIC is currently maintained by EPIC Software Labs (ESL), comprised of Jeremy Nelson, Jake Kuhon, Robert Chady, and a cast of a dozen others.
Main features:
- EPIC is completely safe: There are no hidden trap doors. We value your trust, and will not do anything to abuse it.
- EPIC is programmable: While ircII does contain a wide range of commands and functions, several glaring ommisions exist, which EPIC has attempted to fill, making the ircII language complete, precise, and efficient.
- EPIC supports bots: We do not agree with those who feel that script bots are all the evil of irc, and we feel that scripts bots must not be squelched by those who have the stranglehold of control on irc. EPIC will support bots for as long as we maintain it.
- EPIC is not anal retentive: EPIC allows you to do EVERYTHING that the irc protocol (RFC 1459) allows, and does not place any arbitrary restrictions upon you. EPIC *does* fully comply with the protocol as shipped and does not allow you to do anything that is deemed illegal by the protocol.
- EPIC is complete: EPIC supplies over 100 various functions and commands which allow you to do things very quickly that required very large or slow scripts in the past.
- EPIC is fully ANSI-compliant. Most current versions of the stock client do have full prototyping for all functions, which has the same net effect as the work we have done. We, however, chose to provide both a "old" style (k&r) function header and a "new" style (ansi) function header with every function and provide every extern function a prototype in a header file.
- EPIC is getting smaller and faster. Changes are continually underway to provide a faster client with more functionality while using less CPU cycles. While these may appear to be conflicting goals, the whole point of the EPIC project is to provide the best client that runs as well as can be managed.
Enhancements:
- Change the scary "ERROR --" messages to "INFO --" and hide for dcc and exec.
- Remove hardcoded limits on size of status expandos
- Built in history has been moved to a script implementation
- Translation support fixed for russian users
- Very many commands, functions, sets, moved from builtin to builtins script.
- A new "loadformats" script to use implied on hooks.
- Bug fixes and a multitude of smaller changes.

Magnant is an epic real-time strategy game spanning in the Ant world. Players are managing the growth of anthills.

Starting with minimal resources, players are challenged to build new units, new buildings and collect resources. Players can then build various armies of Ants and slaughter their enemies.

Magnant brings a new concept which may change Real time strategy games concept! Players can collect cards, which enable them to create new units, building or give them special powers.

Players may have different cards and so different abiliites when they play online against opponents. In fact, Magnant is a Trading Card Game where players can fight over a real time strategy environment.

VoR is an exciting Free Software video game, licensed under the GNU GPL. It is developed on GNU Linux but we occasionally release a Windoze binary.

Variations on Rockdodger (VoR) is a fork of Paul Holts little gem Rock Dodger, which has now accumulated enough differences to be worth releasing on its own. The premise is simple: dodge the rocks until you die.

No shields, no weapons, no bonus lives, just pure rockdodgin fun for your spare moments. VoR has ray-traced rocks, a free-scrolling screen, and "real" physics for your ship. Warning: this game is, if anything, harder than the original. It is intended to be a quickie game to kill a few spare moments here and there, not an epic space adventure.

Please contact Jason Woofenden if you could make a Mac binary.

Perilar is a simple, fast computer role-playing game (CRPG), with an epic quest! You will cross a vast monster-infested wilderness to the dungeons to recover ancient weapons and artifacts, then to the dragons lairs, then face the final challenge...

Version 0.4 is a beta release for designing the gameplay, and future versions will have additional art, music, and sound effects.

Save Game Warning: Savefiles from previous versions will not be compatible with later versions until 1.0. At that point, Ill make sure they are always forward-compatible, but it hampers rapid development until then. Sorry for the trouble, but at least youll get to see the new world features in each version!

History

Over a thousand years ago, the world was a peaceful but primitive place. Humans lived in tribal societies, rarely warred, and there were few dangerous animals and no monsters. Your kingdom, Perilar, was one of the safest, as it was protected by four great dragons of Air, Earth, Fire, and Water.

Where the Vampire King came from, nobody knows. He appeared in the far north and turned peaceful farmers into berserker raiders. After conquering the island kingdom of Oradon, he turned their druids to necromancy, raising armies of the dead to war on the next kingdom. Kingdom after kingdom fell, and in each, the people were slain and raised as undead warriors to assault the next kingdom.

As the army of the undead approached Perilar, the dragons closed the kingdom off with a magical seal. For a thousand years, the kingdom has been trapped inside, and none know the fate of the outside world.

In recent times, the seals have begun to fail. The Dragons have not been seen in centuries. Undead and monsters march in towards the castle of King Phalan and the village of Perilar, home to the last free people in the world. A great hero must do something about this, and you are determined to be that hero!

Parallel Port Make project is a tool to build FreeBSD ports in parallel to fully take advantage of modern multi-core and processor machines.

Default: pportmake.py --clean -- cleanup --install -job=2 [port1] [portn]

Example: pportmake.py irc/irssi irc/epic

Advanced: pportmake.py -rSvD -j 10 irc/irssi

-h --help Show this help usage message
-c --clean Clean port before compiling
-C --cleanup Clean port after compiling
-d --deinstall Deinstall ports, implied by reinstall
-f --force Force a port and all dependancies to be installed
-G --noconfig Dont recursively configure options
-i --install Install port (default)
-j n --jobs=n Number of threads to use, 1 or 2 per CPU core
is recommended
Default is 2
-O args --options=foo List of arguments to pass to make.
E.g. -O -DX11=yes -DFOO
-r --reinstall Reinstall port and ALL dependancies
-S --maxspeed Try and speed up by maximising CPU usuage.
This may break some ports, use with caution
-w --noclean Dont make clean before compiling
-W --nocleanup Dont make clean after compiling
-v --verbose Be extra verbose
-V --version Show version information
-D --debug Show some debugging info
-P --pretend Dont actually alter the ports

NOTES: It is currently only safe to run 1 copy of this and not have other ports compiling simultaneously

Encode::PerlIO is a detailed document on Encode and PerlIO.

Overview

It is very common to want to do encoding transformations when reading or writing files, network connections, pipes etc. If Perl is configured to use the new perlio IO system then Encode provides a "layer" (see PerlIO) which can transform data as it is read or written.

Here is how the blind poet would modernise the encoding:

use Encode;
open(my $iliad,:utf8,iliad.utf8);
my @epic = < $iliad >;
print $utf8 @epic;
close($utf8);
close($illiad);

In addition, the new IO system can also be configured to read/write UTF-8 encoded characters (as noted above, this is efficient):

open(my $fh,>:utf8,anything);
print $fh "Any x{0021} string N{SMILEY FACE}n";

Either of the above forms of "layer" specifications can be made the default for a lexical scope with the use open ... pragma. See open.

Once a handle is open, its layers can be altered using binmode.

Without any such configuration, or if Perl itself is built using the systems own IO, then write operations assume that the file handle accepts only bytes and will die if a character larger than 255 is written to the handle. When reading, each octet from the handle becomes a byte-in-a-character. Note that this default is the same behaviour as bytes-only languages (including Perl before v5.6) would have, and is sufficient to handle native 8-bit encodings e.g. iso-8859-1, EBCDIC etc. and any legacy mechanisms for handling other encodings and binary data.
In other cases, it is the programs responsibility to transform characters into bytes using the API above before doing writes, and to transform the bytes read from a handle into characters before doing "character operations" (e.g. lc, /W+/, ...).

You can also use PerlIO to convert larger amounts of data you dont want to bring into memory. For example, to convert between ISO-8859-1 (Latin 1) and UTF-8 (or UTF-EBCDIC in EBCDIC machines):

open(F, ":utf8", "data.utf") or die $!;
while (< F >) { print G }

# Could also do "print G < F >" but that would pull
# the whole file into memory just to write it out again.

More examples:

open(my $f, ":encoding(iso-8859-2)")
open(my $h, ">:encoding(latin9)") # iso-8859-15