Path: chuka.playstation.co.uk!tjs From: tjs@cs.monash.edu.au (Toby Sargeant) Newsgroups: scee.yaroze.programming.codewarrior Subject: Re: Bug in IDE? Date: 26 Apr 1998 12:27:23 GMT Organization: PlayStation Net Yaroze (SCEE) Lines: 38 Message-ID: References: <6hv88b$b017@chuka.playstation.co.uk> NNTP-Posting-Host: indy16.cs.monash.edu.au X-Newsreader: slrn (0.9.5.1 UNIX) On Sun, 26 Apr 1998 12:54:27 +0100, Graham Bisset wrote: >Yup, happened to me as well, running v2 and its >*very* annoying. > >Just suffered another problem with autosave, where each >time you compile, it saves your source file! Very very >annoying and am now having to re-do large parts of the >code to recover. Time that I could have spent learning >more Yaroze stuff, but now having to 'fix' my code *grrrr* losing source really sucks, doesn't it? :( The problem is that the compiler backend is going to need a source file to work from. while it theoretically could compile from a temporary file, or from memory, this would cause lots of other problems, such as external debuggers not havving access to the source, symbols needing to reference both text files and in-core source images, makefiles and projects having much more difficulty keeping track of dependencies and modification dates, and heaps of other things too. every ide i've ever seen writes out source to disk before compiling. what i suggest doing is using an editor (such as vim or emacs) that allows you to specify a script that runs every time a file is saved. then you just get your hands on a version control system like rcs (which I'm sure has been ported to win32 by now), and then check in the source every time the file is written. there are some problems with this idea (you end up with bazillions of revisions of each file), but on the whole, if you're prone to deleting or otherwise screwing up your source code on a regular basis, like i am, then it's a real godsend. >This prevents you from going back to an old version! only if you haven't got an old version lying about :) >Graham toby.