Re: Disassembler
- From: "Oliver Wong" <owong@xxxxxxxxxxxxxx>
- Date: Mon, 27 Feb 2006 17:49:40 GMT
"Howard Brazee" <howard@xxxxxxxxxx> wrote in message news:lhd602hs3ie1rgrfbp0js4vm4kd13q0n9h@xxxxxxxxxx
On Mon, 27 Feb 2006 11:00:10 -0600, Peter Lacey <lacey@xxxxxxx> wrote:
Don't start that again! It isn't every shop that has the luxury of no
inherited programs. Are you also saying that compiled objects never get
lost?????
We're moving towards a Java environment for much of our code. I went
to modify a method and first did a search to determine where the code
was copied - and found 161 copies of a file which I had created, which
was copied by the trunk and branches and a bunch of places that I
don't get. I'm told not to worry about it, but that's hard from my
background.
The code in these are not all the same.
Sounds like you're using a source version control system. These systems keep a copy of every version of the source code you've written. So if you've comitted 100 changes to the files, they'll be 100 copies of the file lying around[*]. "Branch" and "Trunk" are terms frequently used in such system.
See:
http://en.wikipedia.org/wiki/Version_control_system
http://en.wikipedia.org/wiki/Concurrent_Versions_System
http://en.wikipedia.org/wiki/Subversion_%28software%29
- Oliver
[*] Actually, in practice, various compression mechanisms are used. For example, one "master copy" might get stored, and the other 99 files just describe the deviations from the master copy or from each other, rather than containing the whole file verbatim.
.
- References:
- Disassembler
- From: Alistair
- Re: Disassembler
- From: CG
- Re: Disassembler
- From: Pete Dashwood
- Re: Disassembler
- From: Peter Lacey
- Re: Disassembler
- From: Pete Dashwood
- Re: Disassembler
- From: Peter Lacey
- Re: Disassembler
- From: Howard Brazee
- Disassembler
- Prev by Date: debugging
- Next by Date: dubbuging that script
- Previous by thread: Re: Disassembler
- Next by thread: Re: Disassembler
- Index(es):
Relevant Pages
|