Easy way to store source code?

[TheCreator]

Kaduria has 44K and Teemu 19K.

The larger project seems to be abandoned, why did you stop working on it? Wasn't it because of bad code?

Untitled/Fame has comparable size (47K without GUI framework and libraries). When it exceeded 30K (a year ago), I decided to start using version control. Before that point I also thought I didn't need version control for just one programmer. Now I can see how wrong it was. Give it a try, it costs nothing. 20 minutes of setting things up, then profits.

[Krice]

The larger project seems to be abandoned, why did you stop working on it? Wasn't it because of bad code?

It's not abandoned and the source code is almost entirely modern data-driven C++. It's much better than you can imagine with your limited abilities.

Untitled/Fame has comparable size (47K

Is Fame a 7DRL?

[XLambda]

Untitled/Fame has comparable size (47K without GUI framework and libraries). When it exceeded 30K (a year ago), I decided to start using version control. Before that point I also thought I didn't need version control for just one programmer. Now I can see how wrong it was. Give it a try, it costs nothing. 20 minutes of setting things up, then profits.

I had svn/tsvn set up in under 10 minutes iirc. It's a solid VCS, and tsvn is especially nice because it integrates with the Windows GUI. I can only recommend it, been using it for years.

[TheCreator]

Is Fame a 7DRL?

More like 12YRL .

I had svn/tsvn set up in under 10 minutes iirc.

That's right, and another 10 minutes for configuring SvnServe, so that my 2D artist can use the same repository, too.

[Krice]

Untitled/Fame has comparable size (47K without GUI framework and libraries). When it exceeded 30K (a year ago), I decided to start using version control.

I was reading Fame thread and looks like you have problem with bugs. So, version control didn't take care of them, right?

[TheCreator]

I was reading Fame thread and looks like you have problem with bugs. So, version control didn't take care of them, right?

Has anybody said, in this thread or anywhere else, that version control automatically deals with bugs? It just helps programmers, it doesn't replace them.

[Krice]

that version control automatically deals with bugs?

Isn't it exactly what was said: when you detect a bug you can go back to earlier code that didn't have it. It's automatic, you don't have to find the bug at all. However I believe it's not that simple.

[TheCreator]

Isn't it exactly what was said: when you detect a bug you can go back to earlier code that didn't have it. It's automatic, you don't have to find the bug at all. However I believe it's not that simple.

You can do that, but it wouldn't fix the bug. You only revert your changes if you feel they were a complete disaster. If you need to fix a bug, it might be useful to compare your current revision of the code with some revision from the past. This is what I meant.

[guest509]

  To store your source code you should use a 3.5" floppy.

[Krice]

To store your source code you should use a 3.5" floppy.

Kaduria has seen that time when 3.5" floppy was a viable storage unit. I still have those disks somewhere with early versions of Kaduria.

[XLambda]

To store your source code you should use a 3.5" floppy.

Kaduria has seen that time when 3.5" floppy was a viable storage unit. I still have those disks somewhere with early versions of Kaduria.

Aww. I grew up with these sweet little things...  I even have an old 8" floppy on my wall that's older than me.

[mrrstark]

To store your source code you should use a 3.5" floppy.

Kaduria has seen that time when 3.5" floppy was a viable storage unit. I still have those disks somewhere with early versions of Kaduria.

Aha! That's why you're so averse to revision control. Modern computers use so-called "hard" disks, or even "networks" that make tracking changes much faster now than digging through your meticulous stack of floppies.



Once you get used to how fast these new technologies work, revision control can really save you time developing & experimenting!

[guest509]

  In junior high they told me the 3.5" floppy was a 'hard disk'. The 8" was a floppy disk.

  My 'computer' class was just a typing class, and my teacher was a hunt and peck master.

[siob]

that version control automatically deals with bugs?

Isn't it exactly what was said: when you detect a bug you can go back to earlier code that didn't have it. It's automatic, you don't have to find the bug at all. However I believe it's not that simple.

In theory - and there are systems that do this - you can automatically remove a bug if you combine `git bisect` with unit tests. I have never met anyone who had such a sophisticated setup but my linux magazine tells me some people do that.

What you do with git bisect, is you make a binary search for the one change which introduced the bug. You start by telling git the version number of the working code, and a version number for broken code. And git will interactively let you binary search through the versions in between until you find the one commit, which introduced the bug.

This is much more sophisticated then what you usually do. Even if you have SVN or CVS or whatever: step back in time, undo change after change, until you find a version which works; then look at what you changed... that's often 99% of finding a bug.

[TheCreator]

In theory - and there are systems that do this - you can automatically remove a bug if you combine `git bisect` with unit tests. I have never met anyone who had such a sophisticated setup but my linux magazine tells me some people do that.

Damn, this is crazy or I am missing something here. If one is able to write unit tests that would detect a bug, why not to run them *before* the code is committed?

Aww. I grew up with these sweet little things...  I even have an old 8" floppy on my wall that's older than me.

That's bigger than my screen! I remember 5.25" disks, but I was afraid of storing data on something I could bend. 3.5" floppies were fine, but they would always have some bad sectors every time you moved them from computer to computer, so it wasn't the best possible way to store code .