IRC protocol. It is designed to be small, fast, portable and compatible to RFC
standards, and most IRC clients.
libircclient features include:
* Full multi-threading support.
* Single threads handles all the IRC processing.
* Support for single-threaded applications, and socket-based applications,
which use select()
* Synchronous and asynchronous interfaces.
* CTCP support with optional build-in reply code.
* Flexible DCC support, including both DCC chat, and DCC file transfer.
* Can both initiate and react to initiated DCC.
* Can accept or decline DCC sessions asynchronously.
* Plain C interface and implementation
(possible to use from C++ code, obviously)
* Compatible with RFC 1459 and most IRC clients.
* Free, licensed under LGPL license.
* Good documentation and examples available.
WWW: http://libircclient.sourceforge.net/
PR: ports/129278
Submitted by: Julien Laffaye <kimelto at gmail.com>
they can not be introspected with DBIx::Class. Many-to-many
relationships are actually just a collection of convenience methods
installed to bridge two relationships. This DBIx::Class component
can be used to store all relevant information about these
non-relationships so they can later be introspected and examined.
This module is fairly esoteric and, unless you are dynamically
creating something out of of a DBIC Schema, is probably the wrong
solution for whatever it is you are trying to do. Please be advised
that compatibility is not guaranteed for DBIx::Class 0.09000+. We
will try to mantain all compatibility, but internal changes might
make it impossible.
WWW: http://search.cpan.org/dist/DBIx-Class-IntrospectableM2M/
This can be exploited to crash the service by sending specially crafted
requests to the default port 2207/TCP.
PR: 129097
Submitted by: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
Approved by: maintainer
Security: http://www.vuxml.org/freebsd/37940643-be1b-11dd-a578-0030843d3802.html
CornerDelegate object and sends it messages of the form -enterTopLeft and
-exitTopLeftAfter: for each corner, where the exit message takes the number of
seconds the mouse spent in that corner as an argument.
The delegate simply ignores these messages by default. A category on this
object, however, can be provided. If you store a Smalltalk script in the
"CornerScript" default as a string object then this will be loaded
automatically and compiled. If this contains a category on CornerDelegate then
the Smalltalk implementation will be called instead. A trivial example might
log a message when the corner was entered was called:
$ defaults write Corner CornerScript \
"CornerDelegate extend [ enterTopLeft [ 'Script called' log. ] ]"
WWW: http://www.etoile-project.org/
It turns Unix scripts into GNUstep system services.
Scripts should be put under
~/GNUstep/Library/ApplicaitonSupport/ScriptServices/
Whenever new scripts are installed, you need to update services by doing
`openapp ScriptServices --update`
A default script using `bc` comes with ScriptServices.
More scripts are in Examples directory.
WWW: http://www.etoile-project.org/
