Messing around with the Apple sample project SMJobBless, I got the SMJobBless()
function to work.
I.e. my helper tool is blessed and gets copied to:
/Library/PrivilegedHelperTools/de.mdenkmann.SMJobBlessHelper .
But how to start the helper tool?
(Nothing shows up in Activity Monitor, nothing is
On Mar 17, 2012, at 11:58 PM, Luther Baker wrote:
> I was ruminating about it more of a (self) documenting angle as opposed to
> runtime enforcement ... and indeed, its application in C++ is what I'm was
> thinking of.
Well that's fine, but Objective-C and Cocoa predate const by many years.
--
Obj-C and Cocoa don't support "const" because they are older?
On Sun, Mar 18, 2012 at 9:44 AM, Scott Ribe wrote:
> On Mar 17, 2012, at 11:58 PM, Luther Baker wrote:
>
> > I was ruminating about it more of a (self) documenting angle as opposed
> to
> > runtime enforcement ... and indeed, its appl
On Mar 18, 2012, at 12:01 PM, Luther Baker wrote:
> Obj-C and Cocoa don't support "const" because they are older?
Const showed up in C in around '89 or '90. Retrofitting const into large
libraries that were designed without it is an absolute nightmare because of the
cascading changes required.
On 2012 Mar 18, at 03:20, Gerriet M. Denkmann wrote:
> SMJobBless
Wrong email list for SMJobBless. Use apple-c...@lists.apple.com.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the
On Mar 17, 2012, at 10:58 PM, Luther Baker wrote:
> I was ruminating about it more of a (self) documenting angle as opposed to
> runtime enforcement …
Cocoa’s idioms are different. In Cocoa you use mutable vs. immutable container
types to indicate this. So if a method parameter is NSMutableStr
On Mar 18, 2012, at 11:01 AM, Luther Baker wrote:
> Obj-C and Cocoa don't support "const" because they are older?
More because they weren’t designed around it. And because the way C++ does
‘const’ gets really problematic in a dynamic OOP language like Obj-C.
Say you added ‘const’ object pointe
On Mar 18, 2012, at 3:20 AM, Gerriet M. Denkmann wrote:
> Messing around with the Apple sample project SMJobBless, I got the
> SMJobBless() function to work.
> I.e. my helper tool is blessed and gets copied to:
> /Library/PrivilegedHelperTools/de.mdenkmann.SMJobBlessHelper .
>
> But how to star
No no, you've both been very helpful. The time lines and "Mutable" thoughts
are great points and more than answer my underlying question.
Understanding a bit of the history goes along way when trying to
rationalize (and adhere to) current conventions.
Many Thanks!
-Luther
On Sun, Mar 18, 2012 a
On Mar 18, 2012, at 1:42 PM, Kurt Revis wrote:
> "ssd" has apparently gone missing, but BetterAuthorizationSample is still
> around. A few google searches should help you find them.
The “ssd” sample code is still around as well. It’s just tricky to find — and
the fact that Google searching for
I think you've nailed it. Immutability is certainly a good concept, but
including ideas from C++ is not a good idea because concepts are usually
perverted in C++ (and even C - ALGOL carefully removed the junk out of FORTRAN
and assembler but C, just put that garbage back in.) Concepts need very
"...subtly why C and C++ are poor languages..."
1) Is that why most modern operating systems, especially the ones that run in
data centers are written in C?
2) Isn't Objective-"C" a supper set of C, so does that make Objective-C a bad
language as well?
Isn't Mutability just another word for
A recent email from xamarin to me ('cause i bought their MonoTouch thingy)
recently notified me that a change in 5.1 means developers can no longer write
to console. And some other blah, blah, blah...
On Mar 13, 2012, at 7:37 PM, Jonas Maebe wrote:
>
> On 13 Mar 2012, at 23:08, Jens Alfke wrot
On Mar 14, 2012, at 2:09 PM, Wade Tregaskis wrote:
>> I don't like the idea of a multithreaded aproach by default, because as a
>> general rule, you
>> should not make your application multithreaded unless you have a good
>> reason.
>
> b) This convenientional wisdom is, in my humble opinion, a
At 1:40 PM -0700 3/14/12, JongAm Park wrote:
On 3/14/2012 10:27 AM, Scott Ribe wrote:
On Mar 14, 2012, at 11:23 AM, JongAm Park wrote:
it didn't sound harsh in a jungle with full of male creatures.
LOL! And you said your English was not so good. That was great!
Well, I was not born in Englis
With my recent battles against memory warnings and deleted views, I'm
auditing my code to make sure that nothing tries to access controls while
the view is unloaded. Is it typical to enclose a lot of screen-validation
routines and control access in a if([self isViewLoaded])statement?
_
16 matches
Mail list logo
