This is a port of the ircd-ratbox IRC daemon.
ircd-ratbox is the primary ircd used on EFnet; it combines the stability
of an ircd required for a large production network together with a rich
set of features, making it also suitable for use on smaller networks.
Changes Include:
o Optional SSL support to enable encrypted connections between clients
and servers, as well as server to server links.
o Add support for SSL only channels, channel mode +S.
o sqlite3 for handling and storing k/x/d lines.
o Support for global CIDR limits.
o Added adminwall allowing admins to broadcast messages to each other.
o Creation of new library archive 'libratbox'.
o Support for forced nick changes (instead of collision kills).
o New ssld and bandb processes for SSL connections and ban checking;
these allow ratbox-3 to make better use of multi-processor systems.
This EBNETD distribution contains three server commands: ebnetd, ndtpd
and ebhttpd. They are servers for accessing CD-ROM book on remote host
via TCP/IP.
ebnetd: ebnetd is a server of EBNET protocol which is designed to
communicate with EB Library. For more details about EB
Library.
ndtpd: ndtpd is an NDTP (Network Dictionary Transfer Protocol)
server. The first implementation of the NDTP esrver is
`dserver'. ndtpd has upper compatibility with dserver-2.2.
ebhttpd: ebhttpd is a WWW (World Wide Web) server. It supprts HTTP/1.0
and HTTP/1.1 (Hypertext Transfer Protocol version 1.0 and 1.1).
The servers support CD-ROM books of EB, EBG, EBXA, EBXA-C, S-EBXA and
EPWING formats. The servers can run as a standalone daemons by
default, but can also run as children of `inetd'.
In addition, you must follow the licenses of your CD-ROM books. Though
EBNETD is free software, your books may not be free. Don't open your
books to unlicensed hosts nor users.
libskk -- a library to deal with Japanese kana-to-kanji conversion method
Features:
* Support basic features of SKK including new word registration into
dictionary, completion, numeric conversion, abbrev mode, kuten input,
hankaku-katakana input, Lisp expression evaluation (concat only),
and re-conversion.
* Support various typing rules including romaji-to-kana, AZIK, TUT-Code,
and NICOLA.
* Support various dictionary types including file dictionary (such as
SKK-JISYO.[SML]), user dictionary, skkserv, and CDB format dictionary.
* GObject based API with gobject-introspection support.
* Experimental support for intelligent kana-to-kanji conversion based
on Viterbi algorithm.
Documentation:
* file:tests/context.c for basic usage
* http://du-a.org/docs/libskk/libskk/ for Vala binding reference
* http://du-a.org/docs/gtk-doc/libskk/html/ for C binding reference
This is jikes, a java source to byte-code compiler. The compiler has been
made available by IBM under their open-source license, please see:
for details. To operate, the CLASSPATH environment variable must typically
be set to a colon-delimited list of source directories, class directories,
or zip files. Note that jikes will complain if a non-existant directory or
file is specified in CLASSPATH.
===============
// This software is subject to the terms of the IBM Jikes Compiler Open"
// Source License Agreement available at the following URL:"
// http://www.ibm.com/research/jikes."
// Copyright (C) 1996, 1998, International Business Machines Corporation"
// and others. All Rights Reserved."
// You must accept the terms of that agreement to use this software."
D is a systems programming language. Its focus is on combining the power and
high performance of C and C++ with the programmer productivity of modern
languages like Ruby and Python. Special attention is given to the needs of
quality assurance, documentation, management, portability and reliability.
The D language is statically typed and compiles directly to machine code. It's
multiparadigm, supporting many programming styles: imperative, object oriented,
and metaprogramming. It's a member of the C syntax family, and its appearance
is very similar to that of C++.
It is not governed by a corporate agenda or any overarching theory of
programming. The needs and contributions of the D programming community form
the direction it goes.
Coco/R combines the functionality of the well-known UNIX tools lex and yacc,
to form an extremely easy to use compiler generator that generates recursive
descent parsers, their associated scanners, and (in some versions) a driver
program, from attributed grammars (written using EBNF syntax with attributes
and semantic actions) which conform to the restrictions imposed by LL(1)
parsing (rather than LALR parsing, as allowed by yacc). The user has to add
modules for symbol table handling, optimization, and code generation in
order to get a running compiler. Coco/R can also be used to construct other
syntax-based applications that have less of a "compiler" flavour.
Coco/R is available in Oberon, Modula-2, Pascal, Delphi, C, Java and C#
versions. This port only builds the C/C++ version.
Seed7 is an extensible general purpose programming language designed by Thomas
Mertes. It is a higher level language compared to Ada, C/C++ and Java.
In Seed7 new statements and operators can be declared easily. Functions with
type results and type parameters are more elegant than a template or generics
concept. Object orientation is used where it brings advantages and not in
places where other solutions are more obvious. Although Seed7 contains several
concepts from other programming languages, it is generally not considered a
direct descendant of any other programming language.
Major features include:
- user defined statements and operators,
- abstract data types,
- templates without special syntax,
- OO with interfaces and multiple dispatch,
- statically typed,
- interpreted or compiled,
- portable,
- runs under Linux/Unix/Windows.
The Glasgow Haskell Compiler is a state-of-the-art, open source, compiler and
interactive environment for the functional language Haskell. Highlights:
* Supports the entire Haskell 2010 language plus a wide variety of
extensions.
* Has particularly good support for concurrency and parallelism, including
support for Software Transactional Memory (STM).
* Generates fast code, particularly for concurrent programs.
* Works on several platforms including FreeBSD, Windows, Mac, Linux, most
varieties of Unix, and several different processor architectures.
* Has extensive optimisation capabilities, including inter-module optimisation.
* Compiles Haskell code either directly to native code or using LLVM as a
back-end. It can also generate C code as an intermediate target for porting
to new platforms. The interactive environment compiles Haskell to bytecode,
and supports execution of mixed bytecode/compiled programs.
* Profiling is supported, both by time/allocation and various kinds of heap
profiling.
* Comes with several libraries, and thousands more are available on Hackage.
The libjit library implements Just-In-Time compilation functionality. Unlike
other JIT's, this one is designed to be independent of any particular virtual
machine bytecode format or language. The hope is that Free Software projects
can get a leg-up on proprietry VM vendors by using this library rather than
spending large amounts of time writing their own JIT from scratch.
This JIT is also designed to be portable to multiple archictures. If you run
libjit on a machine for which a native code generator is not yet available,
then libjit will fall back to interpreting the code. This way, you don't need
to write your own interpreter for your bytecode format if you don't want to.
Scm conforms to Revised^5 Report on the Algorithmic Language Scheme and
the IEEE P1178 specification.
SLIB is a portable Scheme library which SCM uses.
SLIB-PSD is a portable debugger for Scheme (requires emacs editor).
The init file is hard-coded as /usr/local/lib/scm/Init.scm.
Alternatively, one can set the environment variable SCM_INIT_PATH to the
pathname of Init.scm.
The library files are in /usr/local/lib/scm/slib. Alternatively, one can
set the environment variable SCHEME_LIBRARY_PATH to the slib directory.
Remember to use a trailing / on the pathname.
By default -DSICP is turned on, with the expectation that this is the
major reason for this port. This means test.scm will fail on three tests
in section 6.1. Where strict R4S compliance is important, recompile
without the SICP flag.