constructor for 'E' must explicitly initialize the base class 'C' which does not have a default constructor

2013-01-18 Thread Rick Mann
Can anyone explain this error? It sure looks to me like all the base class constructors are being explicitly called. http://pastebin.com/cVMmgqCZ $ clang Test.cpp Test.cpp:40:5: error: constructor for 'E' must explicitly initialize the base class 'C' which does not have a default

Re: constructor for 'E' must explicitly initialize the base class 'C' which does not have a default constructor

2013-01-18 Thread Rick Mann
Okay, I've learned why it has to be this way, but it sure doesn't seem right to me, especially when it's evident from the code (in this case) which constructor to call. -- Rick On Jan 18, 2013, at 1:28 , Rick Mann rm...@latencyzero.com wrote: Can anyone explain this error? It sure looks to

Re: constructor for 'E' must explicitly initialize the base class 'C' which does not have a default constructor

2013-01-18 Thread John McCall
On Jan 18, 2013, at 1:28 AM, Rick Mann rm...@latencyzero.com wrote: Can anyone explain this error? It sure looks to me like all the base class constructors are being explicitly called. http://pastebin.com/cVMmgqCZ This is off-topic for this list, but since I'm here anyway, I'll

Re: constructor for 'E' must explicitly initialize the base class 'C' which does not have a default constructor

2013-01-18 Thread Rick Mann
On Jan 18, 2013, at 2:18 , John McCall rjmcc...@apple.com wrote: This is off-topic for this list, but since I'm here anyway, I'll answer. In the future, though, please take this to a venue that's more specific to C++. Well, I am developing a Cocoa app, using Objective-C++ and clang (via

Re: NSString and file system Re: AppleScript in Sandboxed App

2013-01-18 Thread Mike Abdullah
On 16 Jan 2013, at 17:40, Quincey Morris quinceymor...@rivergatesoftware.com wrote: On Jan 16, 2013, at 09:12 , jonat...@mugginsoft.com jonat...@mugginsoft.com wrote: To be honest I rarely remember to call -fileSystemRepresentation. The docs seem to indicate that its only purpose is to

Re: constructor for 'E' must explicitly initialize the base class 'C' which does not have a default constructor

2013-01-18 Thread Jens Alfke
On Jan 18, 2013, at 2:24 AM, Rick Mann rm...@latencyzero.com wrote: Some stuff I read online suggested it might be a clang bug. I considered the Xcode list, but figured since this was more in the language than the tool, I asked here. Perhaps by that reasoning, I should've at least posted

UITapGestureRecognizer timeout

2013-01-18 Thread Eric E. Dolecki
I have a UITapGestureRecognizer - when you touch, don't move for a bit release, the tap still fires. Too long a time. I think it's around 0.35 seconds. I'd love for that tap recognizer to be invalidated much quicker. Like half of that. How can I accomplish this, or do I just need to roll my own

Maximum size for NSFileWrapper serialization?

2013-01-18 Thread Sebastien Boisvert
I'm trying to initialize a NSFileWrapper with an existing file which is about 3.65GB (gigs), then get the NSData by serializing it, but get the following exception: MyApp[81289:303] can't write int larger than INT_MAX MyApp[81289:303] ( 0   CoreFoundation    0x7fff8d4280a6

Re: Maximum size for NSFileWrapper serialization?

2013-01-18 Thread Sean McBride
On Fri, 18 Jan 2013 13:18:52 -0800, Sebastien Boisvert said: I'm trying to initialize a NSFileWrapper with an existing file which is about 3.65GB (gigs), then get the NSData by serializing it, but get the following exception: MyApp[81289:303] can't write int larger than INT_MAX MyApp[81289:303]

Re: UITapGestureRecognizer timeout

2013-01-18 Thread Quincey Morris
On Jan 18, 2013, at 09:48 , Eric E. Dolecki edole...@gmail.com wrote: I have a UITapGestureRecognizer - when you touch, don't move for a bit release, the tap still fires. Too long a time. I think it's around 0.35 seconds. I'd love for that tap recognizer to be invalidated much quicker. Like