Revision Control Systems are usually more effective at keeping textual data instead of binary. Not that they cannot - but the possibility to make useful diffs, that help the programmer understand what changed and things like that, are obviously tailored around a textual world. And here we come to what impressed me in your post:
Since most of the example are for compiled language like C/C++ where it required linking etc.
You usually don't track compiled objects with revision systems, for the reasons above and, most of all, because the objects are likely to be different in different machines. OTOH, the source code is the same - and it' (usually!) text much like any Perl script (even if it may resemble line noise ;). IIRC, all examples in the CVS manual relate to the sources, except of course the chapter about binary objects :)
Flavio
perl -ple'$_=reverse' <<<ti.xittelop@oivalf
Don't fool yourself.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
