using namespace phr0z3n;

The Phr0z3n Object was first constructed in C++ in 2001.  The code has been constantly rewritten and, henceforth, evolving since, for logical reasons: others, not outdoing, code revision for stability/security and comformity with the ANSI standards and implementation of new features.

Embedded within the Phr0z3n namespace, commonly aliased, namespace Phr0z3nSpace = Phr0z3n, or, using namespace Phr0z3nSpace = Phr0z3n, in C#, are other namespaces, namely:

Phr0z3nMain:
a class declared solely for isolating shared (and other) assembly entry points.

Phr0z3nTime:
containing the 'custom' code (classes, methods, and other objects) used in the most secure time implementation, inspired solely by the upcomming self-authored article: 'Y2K Was Merely A 'Potential' Bug: Y2K Was Nothing To Worry About: January 19, 2038 Is Around The Corner', with sections ported to the C Language in myTimeDate.c.

Phr0z3nLibs:
containing code written to access other libs/assemblies written/implemented by the said dev.

Phr0z3nStream:
containing code written to manipulate the significant standard streams, in the most skillful ways, for desired results.  In the, later derived (and implemented), Phr0z3n.cs, significant emphasis was placed on the System.IO.MemoryStream class, defined in the mscorlib.dll .NET assembly, which is the workhorse for accessing and manipulating custom/external (embedded) assembly objects/resources.

Phr0z3nNet:
containing code used in networking.

Phr0z3nDev:
embedding other namespaces containing projects already developed or currently being developed by the said dev, namely:

Phr0z3nHax:
white hat stuff.

Phr0z3nHax::Hax0r (Phr0z3nHax.Hax0r in Phr0z3n.cs):
gray hat stuff.

Phr0z3nMal:
forensic stuff.

Phr0z3nCrypt0:
top secret stuff.

Phr0z3nTemp:
work in progress.

Phr0z3nBox:
containing code implementing acute error/exception handling (using the MessageBox on Windows).

While the dev will not state how the different codes are 'logically' implemented (including detailed code structure), an example of a 'specific' .NET assembly's entry point is:
internal class Phr0z3nMain { private void Main(){} }

Other derivatives of The Phr0z3n Object are:

Phr0z3nCode:
an IRC freenode.net channel, created by the said dev, regarding developemnt and contains links to code snippets written/used by the said dev.

Phr0z3nBuntu:
an IRC freenode.net channel, created by the said dev, that is dedicated to Ubuntu Linux.

Phr0z3Nix:
an IRC freenode.net channel, created by the said dev, that is dedicated to other Linux/*NIX-based operating systems.

Phr0z3nChess:
Chess as a hobby of the dev.

Phr0z3n.Dev:
the dev's most prominent handle.  Others preferred are:
Phr0z3n.Penguin (*nix-related with many variants),
Phr0z3n.Daemon/Phr0z3nDaemon (BSD-related),
Phr0z3n.Knight/Phr0z3n_Knight/Phr0z3nKnight (preferred on chess servers),
Phr0z3nX (general gaming handle),
or,
simply The.Phr0z3n or Phr0z3n, among others.

NOTE: There is always one realted to a particular (dev) entity.

phr0z3nDev:
the dev's BerliOS.de dev handle.

NOTE: In the cyber-underworld (commonly associated with (the) DarkNet), you usually become wortcode of a prominent handle whenever you have performed, at least one, notable (not necessarily notorious) hack/task.  Upon gaining notoriety, the handle that you used in the event tend to become associated with your real name.  You can always Google 'famous hackers' or 'notorious hackers' and probe the results for their aliases.