MPLAB version control?
Ned Konz email (remove spam text)
On Tuesday 25 February 2003 07:43 pm, Harold Hallikainen wrote:
> Wow! Thanks for the analysis. Can anyone think of a good reason
> MPLAB doesn't store paths as relative, or let you decide how to do
Some guesses, having been a programmer for a commercial software
* Lazy programmers. This is usually the case when you see a binary
file that looks like a memory dump. Such files are rarely portable
from one version to the next of a product without extra work. Effort
saved now will be extra effort later -- for someone else, you hope.
* No requirement for relative paths. "Hmm.. you mean you want to move
* No interest in making an open config format, perhaps because you
could do something interesting with it (like make it easy to use
their competitors' compilers (CCS, for instance)).
GPG key ID: BEEA7EFE
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads
In reply to: <firstname.lastname@example.org>
See also: www.piclist.com/techref/microchip/languages.htm?key=mplab
You must be a member of the
piclist mailing list
(not only a www.piclist.com member) to post to the