[darwinbuild-changes] [73] trunk/darwinxref/DBDataStore.c
source_changes at macosforge.org
source_changes at macosforge.org
Wed Oct 4 01:42:57 PDT 2006
Revision: 73
http://trac.macosforge.org/projects/darwinbuild/changeset/73
Author: ssen
Date: 2006-10-04 01:42:57 -0700 (Wed, 04 Oct 2006)
Log Message:
-----------
Add some more text about how I think property search
should work. We'll need to rationalize this with a real-life
example.
Modified Paths:
--------------
trunk/darwinxref/DBDataStore.c
Modified: trunk/darwinxref/DBDataStore.c
===================================================================
--- trunk/darwinxref/DBDataStore.c 2005-07-12 23:31:54 UTC (rev 72)
+++ trunk/darwinxref/DBDataStore.c 2006-10-04 08:42:57 UTC (rev 73)
@@ -320,6 +320,23 @@
//
// Kluge to globally support build aliases ("original") and inheritance ("inherits") properties.
//
+// ok, this is how this routine should work, even if it doesn't currently. -ssen
+/*
+ Let's say you have build 8A1, 8A2, and 8A3, and each inherits from the previous.
+ Let's say you have "foo" and "foo_prime", where "foo_prime" is a build alias
+ for "foo". If you're searching for "foo" in 8A3, look there first, and if you fail,
+ walk up the build inheritance tree.
+
+ 8A1 foo
+ 8A2 foo foo_prime->foo
+ 8A3 foo
+
+ If you're looking for "foo_prime" in 8A3, we need to look up the entire
+ build inheritance for an overriding property. Along the way, if we find
+ that foo_prime was a build alias, and no property was found, restart the
+ search with "foo"
+
+*/
CFTypeRef _DBCopyPropWithInheritance(CFStringRef build, CFStringRef project, CFStringRef property,
CFTypeRef (*func)(CFStringRef, CFStringRef, CFStringRef)) {
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/darwinbuild-changes/attachments/20061004/25d39e71/attachment-0001.html
More information about the darwinbuild-changes
mailing list