C++ Programmer's Goldmine last call for suggestions

[pgadmin]

C++ Programmer's Goldmine is basically redy for publishing.

This is your chance to provide last minute suggestions
and request new topics and chapters.

The Goldmine collections include several types of information:

1. Code snippets and examples
2. Expert opinions
3. Relevant link collections

A collection consists of a number of chapters on related
issues, such as abstract class, inheritance, multithreading,
Polymorphism, etc.

Each chapter typically contains between 200 and 1000+
articles. Filters are adjusted to make sure the most
relevant articles get in.

Filters are precise and complex. In two words,
they allow finding a needle in haystack.

So, you can request new chapters and specify additional
filters to assist in creation of the most appropriate
set of articles for a chapter.

At the moment, the chapter list is as follows:

Please specify the list of issues or topics.
Be specific and precise in your request so that it does
not bring up all sorts of unrelated articles.

The site is planned to be published within a week from now.

Here is the list of chapters at the moment.
Please add to it if you find something else needs to be
covered.

You can look for example on http://mfcgoldmine.by.ru/index.html

Try to review different articles in different chapters
and notice the issues with text formatting on some articles.

Unfortunately, some people write pretty sloppy articles
with huge blobs of text, without line breaks between
their followup and the original article, long line lengths,
and generally careless style. The result: their articles
are not a great pleasure to read or understand.

Generally, the paragraph size should be limited to separate
different concepts into clearly defined blocks. That makes
it much easier to digest. In today's hectic world, people
are very impatient and will push the next button as soon
as they see the first ugly blob of text.

Finally, current chapter list:

================= Job file begin =====================

;
; C++ Job file
;
; Specify the Initialization file one per line.
; Each job will be run synchronously, one at a time.

ATLCode
ATLExperts

AbstractClassCode
AbstractClassExperts

C#Code
C#Experts

CDialogCode
CDialogExperts

COMExperts

ConcurrencyCode
ConcurrencyExperts

DatabaseCode
DatabaseExperts

EncapsulationCode
EncapsulationExperts

EventCode
EventExperts

ExceptionCode
ExceptionExperts

HashCode
HashExperts

HookCode
HookExperts

; Too many articles on iterator
; IteratorCode
; IteratorExperts

InterfaceCode
InterfaceExperts

InheritanceCode
InheritanceExperts

MemoryCode
MemoryExperts

PolymorphismCode
PolymorphismExperts

ResourceCode
ResourceExperts

SingletonCode
SingletonExperts

SocketCode
SocketExperts

StreamCode
StreamExperts

STLCode
STLExperts

TemplatesCode
TemplatesExperts

ThreadCode
ThreadExperts

TimerCode
TimerExperts

WaitCode
WaitExperts

WSACode
WSAExperts

XMLCode
XMLExperts

================= Job file end =====================

 

[pgadmin]

This is version 2.

Let me edit it a little more to fix some errors and to make it
easier for you to digest. Also, some additional significant points
are added here.

C++ Programmer's Goldmine is basically ready for publishing.

The site is planned to be published within a week from now.
This is your chance to provide the last minute suggestions
and request new topics and chapters.

The site is automatically generated from over 100,000 articles
input stream using powerful filters that allow filtering
in the most precise manner.

The Goldmine collections include several types of information:

1. Code snippets and examples
2. Expert opinions
3. Relevant link collections
4. Reference material (coming real soon now)

A collection consists of a number of chapters (or categories),
on related issues, such as abstract class, inheritance,
multithreading, polymorphism, etc.

Each chapter typically contains between 200 and 1000+
articles.

Filters are adjusted to make sure the most relevant
articles get in. It is produced out of input stream of
over 100k articles. So, we have a filtering factor
approaching 3 orders of magnitude. We could go upto 8
orders of magnitude currently. But there is no limit
in principle.

Filters are precise, complex and high performance.
In two words, they allow finding a needle in haystack
with orders of magnitude better performance than
regular expressions.

So, you can request some new chapters or specific topics
and specify the filters to assist in creation of the most
appropriate set of articles for a chapter.

Please be specific in your filters to make sure the
result won't bring up all sorts of irrelevant articles.
You can specify if upper/lower case letters are significant.

Example filter specification:

abstract class & inheritance & polymorph, interface

Above, the "abstract class" is matched as a whole.
It is called a keyword phrase. Keyword phrase consists
of multiple keywords.

So, the filtering process results in articles, containing
the abstract class AND inheritance AND polymorph OR interface
(comma is a keyword phrase separator).

Notice: polymorph above. It will match polymorphism and
polymorphic also.

You can specify if words are to be matched STARTING and/or
ENDING (or both) on a word boundary, delimited by standard
delimiters.

Upper/lower case could be specified as significant.

So, the above querry would be specified as:

Query:

abstract class & inheritance & polymorph, interface

Search type: body AND headers
Headers Subject: abstract class, inheritance
Headers From: (e-mail address removed), (e-mail address removed)
Case: significant
Word boundary start: yes (significant)
Word boundary end: no (insignificant)

You can also specify the headers in the same querry.
They could be either ANDed or ORed with the body, meaning
If body filter matches AND header filter matches.

You can provide the association lists. But lets skip it
for now.

Be specific and precise in your request so that it does
not bring up all sorts of unrelated articles.

You can look for example at:

http://mfcgoldmine.by.ru/index.html

Try to review different articles in different chapters
and notice the issues with text formatting on some articles.

Finally, the current chapter list:

================= C++ Job file begin =====================

;
; C++ Job file
;
; Specify the Initialization file one per line.
; Each job will be run synchronously, one at a time.

ATLCode
ATLExperts

AbstractClassCode
AbstractClassExperts

C#Code
C#Experts

CDialogCode
CDialogExperts

COMExperts

ConcurrencyCode
ConcurrencyExperts

DatabaseCode
DatabaseExperts

EncapsulationCode
EncapsulationExperts

EventCode
EventExperts

ExceptionCode
ExceptionExperts

HashCode
HashExperts

HookCode
HookExperts

; Too many articles on iterator
; IteratorCode
; IteratorExperts

InterfaceCode
InterfaceExperts

InheritanceCode
InheritanceExperts

MemoryCode
MemoryExperts

PolymorphismCode
PolymorphismExperts

ResourceCode
ResourceExperts

SingletonCode
SingletonExperts

SocketCode
SocketExperts

StreamCode
StreamExperts

STLCode
STLExperts

TemplatesCode
TemplatesExperts

ThreadCode
ThreadExperts

TimerCode
TimerExperts

WaitCode
WaitExperts

WSACode
WSAExperts

XMLCode
XMLExperts

================= Job file end =====================

Note on writing style:

Many people do not realize their article become available
worldwide on many different sites, servers, search engines
and libraries and will stay there forever.

When they write something, they may not even consider
that it is better to take your time and describe some
topic completely so it becomes a reference material
to be used for generations to come.

Instead, they write cryptic articles that, when viewed
by themselves, may not even make much sense to someone,
who is not reading it on Usenet by following a thread.

Some people strip most of the article they followup on,
and it becomes virtually impossible to understand what
they are talking about. Because this article may just
appear somewhere by itself, without the preceeding
articles in a thread.

Keep it in mind.

Again, it is better to write a thorough and detailed
article to put the issue to rest once and for all,
instead of saying the same thing again and again.

You can simply refer people to that original article
instead of doing it from top again, wasting your own
time and energy and producing very lil additional
information with net effect of close to 0.

Unfortunately, some people write pretty sloppy articles
with huge blobs of text, without line breaks between
their followup and the original article, long line lengths,
and generally careless style. The result: their articles
are not a great pleasure to read or understand.

Generally, the paragraph size should be limited to separate
different concepts into clearly defined blocks. That makes
it much easier to digest. In today's hectic world, people
are very impatient and will push the next button as soon
as they see the first ugly blob of text.