On Feb 25, 2012, at 6:50 PM, R wrote:
> I would like to archive the file in pieces update the file rather
> than write an entire new file each time.
> Is there a good way to just write "object for key" to a file?
Yes: Use a database. That’s literally exactly what you’re describing. You have
I have a large NSMutableDictionary that houses UIImages for memberID
keys.
I'm unArchiving the file using blocks and queues to bring to the data
out off of the main thread.
I would like to archive the file in pieces update the file rather
than write an entire new file each time.
Is there a g
On Thu, Feb 23, 2012 at 6:16 AM, William Squires
wrote:
From what I've read, the NSStepper has a bug (though practically,
you'll never see it); if one were to click the up or down arrow on the
control 2^32 times (assuming it's value is a 4-byte signed int,and is
initialized to 0), it would
On 2/24/12, Sean McBride wrote:
> On Fri, 24 Feb 2012 10:36:51 -0700, Keary Suska said:
>
>>I don't believe this is the case. There can be funny issues with BOOL
>>types, such that BOOL == YES is an inadvisable construct, since your
>>BOOL could be an integer of any value.
>
> Indeed, and it's ext
On Feb 25, 2012, at 6:29 AM, Scott Ribe wrote:
> (!0) evaluates to 1.
I've seen it evaluate to -1 in one compiler some time back when stored in a
signed integer bit field variable.
--
Gary L. Wade (Sent from my iPhone)
http://www.garywade.com/
___
C
On Feb 25, 2012, at 7:56 AM, Kyle Sluder wrote:
> …converting a pointer to integer is not guaranteed to result in a
> representation that fits in any size of integer…
You can use uintptr_t for such purposes, which is supposed to be defined in
stdint.h.
--
Gary L. Wade (Sent from my iPhone)
htt
On 25 Feb 2012, at 7:10 AM, Graham Cox wrote:
> I was surprised to find I couldn't set whether the color panel displayed the
> opacity slider depending on which colour well was selected. Can anyone think
> of a way I could achieve that? Seems to me that the color well/color panel
> communicatio
On Feb 25, 2012, at 7:45 AM, Scott Ribe wrote:
> On Feb 25, 2012, at 8:38 AM, Kyle Sluder wrote:
>
>> Does Harbison & Steele say that pointers converted to integer have the value
>> zero, or does it say that if(ptr) is identical to if(ptr != 0)?
>
> It explicitly states that null pointers conv
On Feb 25, 2012, at 8:38 AM, Kyle Sluder wrote:
> Does Harbison & Steele say that pointers converted to integer have the value
> zero, or does it say that if(ptr) is identical to if(ptr != 0)?
It explicitly states that null pointers converted to int are 0, and that other
conversions are impleme
On Feb 25, 2012, at 7:38 AM, Kyle Sluder wrote:
> compared to an nether constant expression with the value 0
"Integer," not nether. Silly autocorrect.
--Kyle Sluder
(Sent from my uPas)
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do
On Feb 25, 2012, at 7:26 AM, Scott Ribe wrote:
> On Feb 25, 2012, at 8:23 AM, Kyle Sluder wrote:
>
>> And then show how that jives with footnote 56, which says that the intent of
>> the standard is that null pointers become whatever integer is most similar
>> to the bit pattern used for null p
On Feb 25, 2012, at 8:23 AM, Kyle Sluder wrote:
> And then show how that jives with footnote 56, which says that the intent of
> the standard is that null pointers become whatever integer is most similar to
> the bit pattern used for null pointers, which may or may not be the same as
> that use
On Feb 25, 2012, at 6:22 AM, Scott Ribe wrote:
> I saw your citations. You're ignoring the "Except as previously specified"
> clause at the beginning of the sentence you quote. Null pointers converted to
> int become 0; other pointers are implementation defined.
Please cite where the standard
>
>
>
>> I use numerous colour wells all over my app. Mostly, I want the user to be
>> able to use different alpha values, so I have enabled the opacity control
>> for NSColorPanel globally for the app. But there are one or two places where
>> I don't want that - these are associated with s
> I use numerous colour wells all over my app. Mostly, I want the user to be
> able to use different alpha values, so I have enabled the opacity control for
> NSColorPanel globally for the app. But there are one or two places where I
> don't want that - these are associated with specific colo
On 25/02/2012, at 2:29 PM, Scott Ribe wrote:
> On Feb 25, 2012, at 2:29 AM, David Mirabito wrote:
>
>> Not terribly helpful since the cocoa headers are what they are, but in other
>> codebases I sneak around issue this by setting up the defines:
>>
>> #define FALSE 0
>> #define TRUE (!FALSE)
>
On Feb 25, 2012, at 2:29 AM, David Mirabito wrote:
> Not terribly helpful since the cocoa headers are what they are, but in other
> codebases I sneak around issue this by setting up the defines:
>
> #define FALSE 0
> #define TRUE (!FALSE)
>
> Then something like "if (mybool == TRUE)" acts as ex
On Feb 24, 2012, at 10:53 PM, Kyle Sluder wrote:
> On Feb 24, 2012, at 2:07 PM, Scott Ribe wrote:
>
>> On Feb 24, 2012, at 10:52 AM, Wade Tregaskis wrote:
>>
>>> Though technically speaking it's true, and is thus an argument for actually
>>> using NULL rather than 0
>>
>> No, it's not such an
I use numerous colour wells all over my app. Mostly, I want the user to be able
to use different alpha values, so I have enabled the opacity control for
NSColorPanel globally for the app. But there are one or two places where I
don't want that - these are associated with specific colour wells.
As an added advantage on top of that it can avoid loading existing files into
memory until needed. This is particularly handy when writing document packages
as those files can be written quickly as hard links, rather than loading into
memory and writing out afresh.
Sent from my iPad
On 25 Feb
On 25/02/2012, at 2:47 PM, -Sergei G- wrote:
> I don't quite get the role of NSFileWrapper. It appears to provide a subset
> of NSFileManager functionality. Some of the Apple samples use NSFileWrapper
> to implement bundle support, but it is not clear if that's a requirement or
> just a choic
Not terribly helpful since the cocoa headers are what they are, but in other
codebases I sneak around issue this by setting up the defines:
#define FALSE 0
#define TRUE (!FALSE)
Then something like "if (mybool == TRUE)" acts as expected across all non-zero
values.
Also, IIRC, static analysis
On 24 Feb 2012, at 20:36, Sean McBride wrote:
> On Fri, 24 Feb 2012 10:36:51 -0700, Keary Suska said:
>
>> I don't believe this is the case. There can be funny issues with BOOL
>> types, such that BOOL == YES is an inadvisable construct, since your
>> BOOL could be an integer of any value.
>
>
To me, it breaks one of my golden rules, and exposes one of the things I
dislike about C. Expressions, at least in my mind, should not involve state
change – that's what statements are for.
My rationale behind this is that it makes it easier to read expressions – you
get one more guarantee abo
On Feb 24, 2012, at 15:26 , Scott Ribe wrote:
> Thing is: if(foo) is equivalent to if(foo != 0), which I think results in 0
> being treated as a pointer, not the pointer being cast to int, anyway if
> if(foo) could fail, so could if(foo != 0)... Also I think "Except as
> previously specified...
On Feb 24, 2012, at 2:07 PM, Scott Ribe wrote:
> On Feb 24, 2012, at 10:52 AM, Wade Tregaskis wrote:
>
>> Though technically speaking it's true, and is thus an argument for actually
>> using NULL rather than 0
>
> No, it's not such an argument at all. The compiler guarantees that null
> point
I’ve heard from various subscribers that the list is a slow in propagating
messages.
I believe this is indicative of the number of subscribers at this point. I’ll
let the powers that be know and see what might be done.
In the meantime, cc the poster and they’ll get the answer right away. the li
I don't quite get the role of NSFileWrapper. It appears to provide a subset of
NSFileManager functionality. Some of the Apple samples use NSFileWrapper to
implement bundle support, but it is not clear if that's a requirement or just a
choice of the developer.
Can someone elaborate beyond the o
I also don't think this is in the API.
The relevant information is stored in the Info.plist file for each calendar.
The keys are 'EventContainer' and 'TaskContainer', both boolean.
Best wishes
John Maisey
www.nhoj.co.uk
www.twitter.com/johnmaisey
www.facebook.com/nhojcouk
On 23 Feb
Great thanks everyone I think I got it! :-)
rc
On Feb 25, 2012, at 12:06 AM, Kyle Sluder wrote:
> On Feb 23, 2012, at 5:38 PM, "Rick C." wrote:
>
>> Thanks Jan. What method do you call to make it accept the text? That's
>> maybe what I'm looking for...
>
> As I mentioned before, and is e
On Feb 24, 2012, at 1:08 PM, Nick Zitzmann wrote:
>> I also heard that generally speaking NULL is not necessarily always
>> equal to 0 on all architectures.
>>
>> Thoughts?
>
> Where in the world did you hear that? From the C99 standard, 6.3.2.3
> paragraph 3:
>
> "An integer constant expressi
>if(nil != (self = [super init]))
>
> Myself I find it elegantly brief and imminently readable.
I don't mind it, but to me it begs the question of what it offers over:
self = [super init];
if (self) {
My rationale is, generally you avoid assignments within conditionals becau
32 matches
Mail list logo
