You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/// a set of preference ordered base directories relative to which data files should be searched. This set of directories is defined by the environment variable $XDG_DATA_DIRS.
// $XDG_DATA_DIRS defines the preference-ordered set of base directories to search for data files in addition to the $XDG_DATA_HOME base directory. The directories in $XDG_DATA_DIRS should be seperated with a colon ':'.
1248
+
// $XDG_DATA_DIRS defines the preference-ordered set of base directories to search for data files in addition to the $XDG_DATA_HOME base directory. The directories in $XDG_DATA_DIRS should be separated with a colon ':'.
1249
1249
// If $XDG_DATA_DIRS is either not set or empty, a value equal to /usr/local/share/:/usr/share/ should be used.
/// a set of preference ordered base directories relative to which configuration files should be searched. This set of directories is defined by the environment variable $XDG_CONFIG_DIRS.
// $XDG_CONFIG_DIRS defines the preference-ordered set of base directories to search for configuration files in addition to the $XDG_CONFIG_HOME base directory. The directories in $XDG_CONFIG_DIRS should be seperated with a colon ':'.
1272
+
// $XDG_CONFIG_DIRS defines the preference-ordered set of base directories to search for configuration files in addition to the $XDG_CONFIG_HOME base directory. The directories in $XDG_CONFIG_DIRS should be separated with a colon ':'.
1273
1273
// If $XDG_CONFIG_DIRS is either not set or empty, a value equal to /etc/xdg should be used.
/* HACK - this is to work around the fact that individual domains lose the information about their user/host/app triplet at creation time. We should find a better way to propogate this information. */
112
+
/* HACK - this is to work around the fact that individual domains lose the information about their user/host/app triplet at creation time. We should find a better way to propagate this information. */
@@ -248,7 +248,7 @@ typedef struct { /* A simple struct to maintain ASCII/Unicode versions of t
248
248
} CFVarWidthCharBuffer;
249
249
250
250
251
-
/* Convert a byte stream to ASCII (7-bit!) or Unicode, with a CFVarWidthCharBuffer struct on the stack. false return indicates an error occured during the conversion. Depending on .isASCII, follow .chars.ascii or .chars.unicode. If .shouldFreeChars is returned as true, free the returned buffer when done with it. If useClientsMemoryPtr is provided as non-NULL, and the provided memory can be used as is, this is set to true, and the .ascii or .unicode buffer in CFVarWidthCharBuffer is set to bytes.
251
+
/* Convert a byte stream to ASCII (7-bit!) or Unicode, with a CFVarWidthCharBuffer struct on the stack. false return indicates an error occurred during the conversion. Depending on .isASCII, follow .chars.ascii or .chars.unicode. If .shouldFreeChars is returned as true, free the returned buffer when done with it. If useClientsMemoryPtr is provided as non-NULL, and the provided memory can be used as is, this is set to true, and the .ascii or .unicode buffer in CFVarWidthCharBuffer is set to bytes.
252
252
!!! If the stream is Unicode and has no BOM, the data is assumed to be big endian! Could be trouble on Intel if someone didn't follow that assumption.
253
253
!!! __CFStringDecodeByteStream2() needs to be deprecated and removed post-Jaguar.
/* We must be careful here, because another thread may be trying to allocate this memory at the same time (8203146). This may happen if two threads both attempt to read from a lazily-allocated node. */
133
133
if ((compact ? (cap!=node->info.leaf.capacityInBytes) : (cap>node->info.leaf.capacityInBytes))) {
/* Check again now that we've acquired the lock. We know that we can do this because two simulaneous readers will always pass the same capacity. This is the fix for 8203146. This probably needs a memory barrier. */
135
+
/* Check again now that we've acquired the lock. We know that we can do this because two simultaneous readers will always pass the same capacity. This is the fix for 8203146. This probably needs a memory barrier. */
136
136
if ((compact ? (cap!=node->info.leaf.capacityInBytes) : (cap>node->info.leaf.capacityInBytes))) {
137
137
*((void**)&node->info.leaf.memory) =__CFSafelyReallocateWithAllocator(allocator, node->info.leaf.memory, cap, 0, NULL); // This will free...
138
138
if (__CFOASafe) __CFSetLastAllocationEventName(node->info.leaf.memory, "CFStorage (node bytes)");
/* No need to replace any children, nothing to do for this case */
1258
1258
}
1259
1259
else {
1260
-
/* Got a legitimately new root back. If it is unfrozen, we can just acquire its guts. If it is frozen, we have more work to do. Note that we do not have to worry about releasing any existing children of the root, beacuse __CFStorageDeleteUnfrozen already did that. Also note that if we got a legitimately new root back, we must be a branch node, because if we were a leaf node, we would have been unfrozen and gotten ourself back. */
1260
+
/* Got a legitimately new root back. If it is unfrozen, we can just acquire its guts. If it is frozen, we have more work to do. Note that we do not have to worry about releasing any existing children of the root, because __CFStorageDeleteUnfrozen already did that. Also note that if we got a legitimately new root back, we must be a branch node, because if we were a leaf node, we would have been unfrozen and gotten ourself back. */
1261
1261
storage->rootNode.numBytes=newRoot->numBytes;
1262
1262
storage->rootNode.isLeaf=newRoot->isLeaf;
1263
1263
bzero(&storage->rootNode.info, sizeofstorage->rootNode.info); //be a little paranoid here
// Consider searching for `WoM == 1` when searchingDate is *in* W1 of January. Because we're looking to advance to next month, we could simply add a month, right?
1458
-
// Adding a month from Monday, January 1st lands us on Thursday, February 1st; from Tursday, January 2nd we get Friday, February 2nd, etc. Note though that for January 4th, 5th, and 6th, adding a month lands us in **W2** of February!
1458
+
// Adding a month from Monday, January 1st lands us on Thursday, February 1st; from Thursday, January 2nd we get Friday, February 2nd, etc. Note though that for January 4th, 5th, and 6th, adding a month lands us in **W2** of February!
1459
1459
// This means that if we continue searching forward from there, we'll have completely skipped W1 of February as a candidate week, and search forward until we hit W1 of March. This is incorrect.
1460
1460
//
1461
1461
// What we really want is to skip to the _start_ of February and search from there -- if we undershoot, we can always keep looking.
// <rdar://problem/15420462> "Yesterday" and "Today" now appear in lower case
626
-
// ICU uses middle of sentence context for relative days by default. We need to have relative dates to be captalized by default for backward compatibility
626
+
// ICU uses middle of sentence context for relative days by default. We need to have relative dates to be capitalized by default for backward compatibility
// we default to era 1 if era is missing, however, we cannot just test if the era is 1 becuase we may get era 2 or larger if the year in the string is greater than 60
1579
+
// we default to era 1 if era is missing, however, we cannot just test if the era is 1 because we may get era 2 or larger if the year in the string is greater than 60
1580
1580
// now I just assume that the year will not be greater than 600 in the string
1581
1581
if (__cficu_ucal_get(cal, UCAL_ERA, status) <10) {
// Leopard's implemenation of this always returned true. We should only return true when the conversion is lossless. However, there are some clients who use CFNumber with small unsigned values disguised as signed values. Since there is no CFNumber API yet for unsigned values, we need to accomodate those clients for now. <rdar://problem/6471866>
712
-
// This accomodation should be removed if CFNumber ever provides API for unsigned values. <rdar://problem/6473890>
711
+
// Leopard's implementation of this always returned true. We should only return true when the conversion is lossless. However, there are some clients who use CFNumber with small unsigned values disguised as signed values. Since there is no CFNumber API yet for unsigned values, we need to accommodate those clients for now. <rdar://problem/6471866>
712
+
// This accommodation should be removed if CFNumber ever provides API for unsigned values. <rdar://problem/6473890>
// Leopard's implemenation of this always returned true. We should only return true when the conversion is lossless. However, there are some clients who use CFNumber with small unsigned values disguised as signed values. Since there is no CFNumber API yet for unsigned values, we need to accomodate those clients for now. <rdar://problem/6471866>
732
-
// This accomodation should be removed if CFNumber ever provides API for unsigned values. <rdar://problem/6473890>
731
+
// Leopard's implementation of this always returned true. We should only return true when the conversion is lossless. However, there are some clients who use CFNumber with small unsigned values disguised as signed values. Since there is no CFNumber API yet for unsigned values, we need to accommodate those clients for now. <rdar://problem/6471866>
732
+
// This accommodation should be removed if CFNumber ever provides API for unsigned values. <rdar://problem/6473890>
// The following set of _plist... functions append various things to a mutable data which is in UTF8 encoding. These are pretty general. Assumption is call characters and CFStrings can be converted to UTF8 and appeneded.
287
+
// The following set of _plist... functions append various things to a mutable data which is in UTF8 encoding. These are pretty general. Assumption is call characters and CFStrings can be converted to UTF8 and appended.
0 commit comments