Le 12 août 2012 à 03:16, Jayson Adams a écrit :
>
> On Aug 11, 2012, at 4:51 PM, Graham Cox wrote:
>
>> On 12/08/2012, at 4:18 AM, Jayson Adams wrote:
>>
>>> the porting guide currently states, which is that you may not want to move
>>> to 64-bit
>>
>>
>> What's so hard about moving to 64
For memory addressing, 64 bit should be enough for some times.
For computation, 128 bit is already something from the past as actual Mac
processors provide 256bits register (AVX) ;-)
Le 12 août 2012 à 04:09, koko a écrit :
>
> Is 64-bit the end or will there be 128-bit?
>
>
> -koko
>
>
>
Le 12 août 2012, à 04:09, koko écrivit :
> Is 64-bit the end or will there be 128-bit?
The term "64-bit" is misleading. There are several parameters that can be
quantified by a number of bits: internal width of registers, of the data and
address buses, both internal and external, of the variou
In windowWillUseStandardFrame:defaultFrame: in a subclass of NSDocument (which
is also the delegate of it's window) I want to set the window to just contain a
certain line.
- (NSRect)windowWillUseStandardFrame:(NSWindow *)sender
defaultFrame:(NSRect)defaultFrame
{
// myTextView is
I have worked with PubSub a lot as well but I also did stumble over these
assertions and I could also not work around them. The whole application I
developed had to be put on hold because of this. I reported these assertions
years ago but did get no response. If I had to do it again I would simp
On Aug 12, 2012, at 1:57 AM, Vincent Habchi wrote:
> That’s from the hardware side. Unfortunately, since most people gave up
> programming in assembly (what a loss! ;)) in favor of C, its derivatives, or
> other various high level languages, there was a need to nail down the width
> of various
On Aug 12, 2012, at 4:34 AM, Christian Kienle wrote:
> I reported these assertions years ago but did get no response.
Disclaimer: I wrote about ⅔ of the PubSub framework.
After I left Apple at the end of 2007 I don't think anyone else put any work
into the framework.
> If I had to do it again
On Aug 12, 2012, at 11:29 AM, Jens Alfke wrote:
>> I reported these assertions years ago but did get no response.
>
> Disclaimer: I wrote about ⅔ of the PubSub framework.
> After I left Apple at the end of 2007 I don't think anyone else put any work
> into the framework.
It really seems like t
I talked to an XCode developer at WWDC who agreed that an equivalent of the
"drag the header onto the nib" feature would be a nice addition to XCode 4.
File a bug with Apple, it'll get marked as a dup of rdar://11704722:
>In the standalone Interface Builder app, you can drag a header file onto t
I've hit this a couple of times too. Normally building the app makes the
actions show up in the xib. Not a great solution if your build time is long.
Martin
On 12 Aug 2012, at 20:10, Lee Ann Rucker wrote:
> I talked to an XCode developer at WWDC who agreed that an equivalent of the
> "drag th
How do I get system memory usage numbers within my app?
Charlie Dickman
3tothe...@comcast.net
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa
On Aug 12, 2012, at 3:21 PM, Charlie Dickman <3tothe...@comcast.net> wrote:
> How do I get system memory usage numbers within my app?
What kind of memory usage numbers? There are a lot of different ones — take a
look at the man page for 'top', or at all the different views in Activity
Monitor.
Not a solution at all if you don't build with XCode - and even if we did, it's
not one our localizers could use because they don't do builds.
- Original Message -
From: "Martin Hewitson"
To: "Lee Ann Rucker"
Cc: "Graham Cox" , "cocoa-dev@lists.apple.com Dev"
Sent: Sunday, August 12, 2
Initially I'm interested in system wide memory usage (free, wired,active,
inactive) but following on I might like numbers for just my process.
If hacking through Darwin is the only way to do this than never mind but with
all of the programs out there that include these numbers there must be a bet
14 matches
Mail list logo
