delorie.com/archives/browse.cgi | search |
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1658560993-1394632853=:27761 Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT On Tue, 11 Mar 2014, karl AT aspodata DOT se wrote: >> 2. having self-contained schematic files. > > What's the use case for that, is it only for distributing schematics, > archiving, make your disk tree look nicer or is it for something else > also ? It's a matter of preference and habit. Some people seem to prefer minimizing the risk of inadvertently editing multiple copies of a file while others prefer minimizing the risk of a symbol dependency suddenly being different or lost or just not there when needed. With “non-authoritative embedding”, you will have a copy of the symbol when you need it, won't miss a (potentially incompatible) change in the library but still have a single place where things are stored. >> Maybe the second problem could be solved by "embedding" each symbol the >> first time it is referenced while marking the embedded symbol as >> non-authoritative. This way, the tools could use the included symbol in >> case the library symbol is not found, and otherwise compare the symbol to >> the library version and, if outdated, offer to update it. --8323329-1658560993-1394632853=:27761--
webmaster | delorie software privacy |
Copyright 2019 by DJ Delorie | Updated Jul 2019 |