Home|News blank.gif
When Design Matters CoreLinux++ CoreLinux Consortium
Developer's Corner

CoreLinux++ FAQ

The Corelinux Consortium

Revision: 1.2


This document is the Corelinux++ Frequently Asked Question guide. It should answer any of the questions you asked about Corelinux++ and its development process.


Copyright notice

CoreLinux++ Copyright (c) 1999, 2000 CoreLinux Consortium
Revision: 1.2 , Last Modified: 2000/07/28
This material may be distributed only subject to the terms and conditions set forth in the Open Publication License.

CoreLinux++ and Open Source

Are you really Open Source?

Yes, all of the documentation and graphics are licensed under the Open Publication License, and all of the source code under the Free Software Foundations Lesser General Public License (LGPL).

What are you offering?

At a minimum, a coherent set of standards for Object Oriented Analysis and Design with C++ implentations in Linux. Ultimately we will be providing a set of class libraries that provide other developers with common classes, patterns, framework, and service abstractions.

Will the class libraries and frameworks be portable?

Our only goal is to be portable across Linux platforms (distributions and hardware). Because of this we can achieve native performance in the class implementations and avoid the weight gain when trying to be all things to all platforms.

What about the C++ Standards?

We encourage and exploit the standards as set in the ISO 14882 (1998E) C++ Standard.

How are you funded?

Free time, the belief in Open Source, Linux, other organizations' belief in the same, and sweat.

Contacting the CoreLinux++ Consortium

Web Resources

Does CoreLinux++ have a web page?

The CoreLinux++ web site.

What about a project page?

The CoreLinux++ Project Page has links to file downloads, message forums, mailing lists, defect reporting and general information.

Internet Resources

Is there a mailing list?

Go to the Subscription page and follow the directions.

Defect Reporting or Suggestions

How do I report a defect or make a suggestion?

Sign on to the Project Page and select the Bug Report link.

2.3.2: What do the defect groups mean?

We have identified a number of groups for reporting defects, or making suggestions:

Something you would like to see from CoreLinux++ that isn't in plan or already a feature request
Severity 1 Defect
core dump, corrupt data, etc. The REALLY BAD STUFF
Severity 2 Defect
incorrect IO, breaks existing applications, etc
Severity 3 Defect
Class interfaces or implementation not robust enough, compiler errors, etc.

General catch all for other defects not characterized by above.

General Information

File and source code access

Is there an ftp site to get the current tarball?

Anonymous logon to


follow to


Is the source tree available?

The project's CVS tree can be checked out through anonymous (pserver) CVS with the following instruction set. The module you wish to check out must be specified as the modulename. When prompted for a password for anonymous, simply press the Enter key.

cvs -d:pserver:anonymous@cvs.corelinux.sourceforge.net:/cvsroot/corelinux login
cvs -d:pserver:anonymous@cvs.corelinux.sourceforge.net:/cvsroot/corelinux co modulename

Updates from within the module's directory do not need the -d parameter.

Is there another way?

As an alternative, the CoreLinux++ CVS tree is archived daily


C++ Coding Style

Is there a document describing this?

Refer to the Coding Standards page, see (Consortium, 2000a).

Object Oriented Analysis and Design

Is there a document describing the process?

Refer to the Analysis and Design page, see (Consortium, 2000b)..


What do I need to know to build the CoreLinux++ class libraries?

Read the Developers Guide or just run make from the downloaded release /corelinux directory.

I want to be involved, how do I do this?

Join the mailing list, read the CoreLinux++ process documentation, and if you are still interested send e-mail to me

I want to contribute but I don't want to join. Can I do this?

Yes. Use our projects Patch manager facility. We can't promise that it will be incorporated, but it will be reviewed and you will be contacted.

What do I need to know to use the CoreLinux++ binaries?

Examine the examples in /corelinux/src/testdrivers for a start, see following section

Class Library Documentation

Is there documentation of the class libraries?

Under construction by CoreLinux++ Class Reference.

How is the documentation created?

We are juggling between two systems that generate HTML from comments in the source headers. Luckily they both work off the same style of commenting.


The Corelinux Consortium.
The Corelinux C++ Coding Standards.
The Corelinux Consortium, 1.3 edition, May 2000a.

The Corelinux Consortium.
The Corelinux Object Oriented Design Standards.
The Corelinux Consortium, 1.3 edition, May 2000b.

Christophe Prud'homme 2000-08-14

Copyright © 1999, 2000 by CoreLinux Consortium
This material may be distributed only subject to the terms and conditions set forth in the Open Publication License
- contact the webmaster
Powered / Hosted by

NoMagic, inc.
thanks Gary!
Cool OO Sites
  Made with xemacs / php Comments to webmaster blank.gif