Channels ▼

Bob Stout

Dr. Dobb's Bloggers

The evolution of SNIPPETS...

October 06, 2009

...or "Is this your father's SNIPPETS?" Well, yes and no.

Although I've been lax in maintaining the collection and archives in recent years, it has never stopped evolving. As some of you may know, the SNIPPETS collection started out as my own personal collection of guaranteed reusable C code back in the mid- to late-80's. As my career changed, I kept adding to it and revising it to support new requirements. For example:

  • The SNIPPETS archive originally consisted of only C code. Although C remains the primary focus, it now also includes C++. Where appropriate and possible everything now compiles in either language. I still used mostly C since my career was embedded systems, where C++ can be a significant factor in unacceptable code bloat, but the collection is targeted at a broader audience. Besides, I also kept on writing PC utilities and Windows made it necessary that SNIPPETS modules work with C++.
  • The SNIPPETS archive was originally targeted at MS/PC-DOS. Obviously, that had to change. The upside of that focus was that SNIPPETS code was useful in systems-level programming. However, as my personal collection evolved, I added explicit support for Win32 and Linux/UNIX/Solaris.
  • Since the 80's was the decade of the Great Compiler Wars, the original SNIPPETS collection had scads of conditional code to support multiple PC compilers. The current collection only supports MSVC++/DMC++ and gcc/g++.
So, what hasn't changed? It's still 100% free code - period! That's totally free for any use, personal or commercial. No commercial restrictions and no GPL-like restrictions. All SNIPPETS code either carries an explicit public domain notice or free unrestricted license. You can do anything you like with it except:
  1. Use it to create a commercial library, or
  2. Try to claim any copyright - it's all either public domain or freely licensed by the copyright holder(s).

Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 


Video