For Programmers: Free Programming Magazines  


Home > Archive > Lisp > December 2004 > Binary -> Source links (was Re: File versioning on TOPS-20, et alia -- by diffs?)









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Binary -> Source links (was Re: File versioning on TOPS-20, et alia -- by diffs?)
Will Hartung

2004-12-23, 4:07 pm

"Christopher C. Stacy" <cstacy@news.dtpq.com> wrote in message
news:u1xdk1k74.fsf@news.dtpq.com...
> Bruce Stephens <bruce+usenet@cenderis.demon.co.uk> writes:
>
> Open Genera :)


Now, as I understand it, Open Genera also was able to link binaries to
source code (for debugging, etc.).

Any ideas how it managed relationships to files with multiple versions on
the disk? Did it track the file version as well as the file name in the
source link (in VMS you'd use "FILE.DAT;123" for an absolute reference)? If
I had a binary bit that was linked to an older source file, but had a more
recent source file (say a yet to be compiled work in progress), would Genera
go to the older file or the current file? If I simply re-evaluated a
function within a source file (say I added 10 lines to it), would the system
be out of sync with all of other functions located below the changed
function in the file until I rebuilt the entire file?

What about code that was simply keyed in to a listener, did Genera keep
track of that code as well?

Having never seen it in action, I don't know what its capabilities were, and
with the dynamics of source code change, and how only fragments of code
would be re-evaluated, I'm just curious how OG managed to pull it all off
(if it indeed did at all...).

Regards,

Will Hartung
(willh@msoft.com)


Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com