unsubscribe
unsubscribe
- Subject: unsubscribe
- From: Craig Morris <email@hidden>
- Date: Mon, 27 Aug 2001 21:24:39 +1000
On Friday, August 24, 2001, at 02:58 AM, cocoa-dev-
email@hidden wrote:
Send cocoa-dev mailing list submissions to
email@hidden
To subscribe or unsubscribe via the World Wide Web, visit
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
or, via email, send a message with subject or body 'help' to
email@hidden
You can reach the person managing the list at
email@hidden
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cocoa-dev digest..."
Today's Topics:
1. Re: Docs (Phillip Mills)
2. Re: NSFileSystemSize (John C. Randolph)
3. Re: Bug in NSString stringWithFormat? (Ondra Cada)
4. Passing variable argument list on to another function (Christian
Mike)
5. Re: Docs (Jonathan Hendry)
6. Re: Help on adding help (Jonathan Hendry)
7. Re: Docs (Ondra Cada)
8. Re: Docs (Ondra Cada)
9. Re: Docs (Ondra Cada)
10. Re: Docs (Todd Heberlein)
11. Re: Passing variable argument list on to another function (Andrew
Pinski)
12. Re: Bug in NSString stringWithFormat? (John C. Randolph)
13. Re: Passing variable argument list on to another function (Ondra
Cada)
14. Re: Passing variable argument list on to another function (Ondra
Cada)
15. RE: Bug in NSString stringWithFormat? (Rainer Brockerhoff)
16. Re: Docs (John C. Randolph)
17. Re: Docs (Jonathan Hendry)
--__--__--
Message: 1
Date: Thu, 23 Aug 2001 12:10:14 -0400
Subject: Re: Docs
From: Phillip Mills <email@hidden>
To: <email@hidden>
On 8/23/01 11:52 AM, "Chuck Toporek" <email@hidden> wrote:
Phillip Mills wrote:
Even finding a person to type in the examples and verify that they
compile
would be a GIANT step in the right direction. I buy a lot of O'Reilly
books, both for work and home. Obviouly, I usually like them or I'd
have
stopped years ago...but I feel like a sucker for having spent money
on this
one. It gives me the feeling that someone saw an opportunity to
"Make Money
Fast" and rushed it out the door with the least attention to quality
and
content possible.
I don't think we (or Apple) were trying to "Make Money Fast" by
publishing that book.
OK, I'll try to think of other reasons for the number of errors, lack of
consistency, and superficial treatment. If you have any, feel free to
offer
them.
I think what's more important here is that we're
listening to our readers and taking your concerns and feedback
seriously. One of my goals is to work on revising "Learning Cocoa" and
to make sure that it meets everyones expectations.
That's a nice, "can't we all just get along," thing to say and,
although I
seriouly applaud any efforts in that direction for the future, I think
you
should consider issuing a recall on the original. :-/
--__--__--
Message: 2
Date: Thu, 23 Aug 2001 08:08:27 -0700
Subject: Re: NSFileSystemSize
Cc: <email@hidden>
To: Michael Stone <email@hidden>
From: "John C. Randolph" <email@hidden>
On Thursday, August 23, 2001, at 07:47 AM, Michael Stone wrote:
On 8/23/01 12:04 AM, John C. Randolph at email@hidden wrote:
On Wednesday, August 22, 2001, at 09:01 PM, Michael Stone wrote:
On 8/22/01 9:45 PM, John C. Randolph at email@hidden wrote:
On Wednesday, August 22, 2001, at 08:35 PM, Michael Stone wrote:
I'm using fileSystemAttributesAtPath:NSHomeDirectory() to get the
total
disk
space via NSFileSystemSize, but it's returning 788MB when I really
have
4700MB. NSFileSystemFreeSize returns a correct value of 2878MB.
Does
anyone
know why NSFileSystemSize is returning an incorrect value?
Isn't NSFileSystemSize supposed to say how much space the filesystem
has
*used*?
If that's the case, it should be returning 2103MB for my system.
Instead, it
returns 788MB.
I believe it's supposed to report the space taken by the tree starting
at the given path. You should get the answer of 2103MB if you called
fileSystemAttributesAtPath:@"/".
I would have thought that, too, but it still gives me 788MB. Are you
seeing
this problem on your system? Has anyone else seen this problem?
Is it possible that there's another consumer of space on this disk that
isn't accounted for? How much do your /tmp and /private/vm directories
account for? Maybe mmap()'d files are involved?
-jcr
"This is not a book to be tossed aside lightly. Rather, it should be
hurled with great force." -Dorothy Parker
--__--__--
Message: 3
From: Ondra Cada <email@hidden>
Date: Thu, 23 Aug 2001 18:10:31 +0200
To: Christian Mike <email@hidden>
Subject: Re: Bug in NSString stringWithFormat?
Cc: Cocoa Development <email@hidden>
Reply-To: email@hidden
Christian,
Christian Mike (CM) wrote at Thu, 23 Aug 2001 10:49:51 -0500:
CM> How do I make a request to Apple to make the
CM>
CM> %[width][.prec]s
CM>
CM> format specifier in NSString (and NSMutableString) work the same as
the C
CM> printf function?
www.apple.com/macosx/feedback (or whatever the URL was)?
You might also try to ask Chris Kane, if he is not fed up yet with us,
including a number of my own stupid private mails sent to him
recently ;)))
Incidentally, I would like to see the bug fixed, too, but my own view
of its
importance (compared with other ones) is quite low.
And BTW, if you will write that, perhaps you might add a feature request
(priority low, too) that the very same specifiers should work the very
same
way for %@, too?
---
Ondra Cada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
--__--__--
Message: 4
From: Christian Mike <email@hidden>
To: "'Cocoa List'" <email@hidden>
Subject: Passing variable argument list on to another function
Date: Thu, 23 Aug 2001 11:15:03 -0500
As you have seen from previous e-mails, I am fighting a difference
between
NSString string formats and printf. I would like to do the following:
[myMutableString myAppendFormat:formatString,argList...];
and write my own function that essentially does:
-(void)myAppendFormat:(NSString *)formatString,...
{
char cString[1024];
va_list argList;
sprintf(cString,[formatString cString],argList);
[self appendString:[NSString stringWithCString:cString]];
}
But this doesn't seem to work quite right. How can I pass the variable
argument list portion of this on to sprintf?
Thanks.
Michael Christian
--__--__--
Message: 5
Date: Thu, 23 Aug 2001 11:16:57 -0500
From: Jonathan Hendry <email@hidden>
To: <email@hidden>
Subject: Re: Docs
On Thursday, August 23, 2001, at 10:34 , Phillip Mills wrote:
On 8/23/01 11:03 AM, "Chuck Toporek" <email@hidden> wrote:
"Learning Cocoa" could be better, but for most, it serves the general
purpose of introducing people to Cocoa and the developer tools. One of
the things I'm working on right now is reviewing and editing the
existing book and trying to find a new author to work with me on a
revision to make it better.
Even finding a person to type in the examples and verify that they
compile
would be a GIANT step in the right direction.
Just curious, did you download the source code from the OReilly website
and try compiling it? Also, did you check the website for errata
listings
and corrections? It says in the preface, "The web site for Learning
Cocoa
lists examples, errata, and plans for future editions. You can access
this page at: http://www.oreilly.com/catalog/learncocoa
The confirmed-errata page is at:
http://www.oreilly.com/catalog/learncocoa/errata/learncocoa.confirmed
They also provide a list of changes in a recent printing:
http://www.oreilly.com/catalog/learncocoa/errata/learncocoa.701
IMHO, O'Reilly bends over backwards compared to most publishers.
--__--__--
Message: 6
Date: Thu, 23 Aug 2001 11:21:39 -0500
From: Jonathan Hendry <email@hidden>
To: email@hidden
Subject: Re: Help on adding help
On Wednesday, August 22, 2001, at 07:50 , Jessica Kahn wrote:
Finally, there's a little tutorial for providing basic online Help
with Apple Help, in the upcoming release of Mac OS X. You'll find
it under /Developer/Documentation/Apple Help/Tutorial/.
Hi Jessica,
Any chance you could let us know which files in /Developer/Documentation
are going to change, or be added? A rough sketch should suffice.
ie, has there
been much added in the TasksAndConcepts branch of the Cocoa docs?
Thanks,
Jon
--__--__--
Message: 7
From: Ondra Cada <email@hidden>
Date: Thu, 23 Aug 2001 18:20:42 +0200
To: Phillip Mills <email@hidden>
Subject: Re: Docs
Cc: <email@hidden>
Reply-To: email@hidden
Phillip,
Phillip Mills (PM) wrote at Thu, 23 Aug 2001 12:10:14 -0400:
PM> >I don't think we (or Apple) were trying to "Make Money Fast" by
PM> >publishing that book.
PM>
PM> OK, I'll try to think of other reasons for the number of errors,
lack of
PM> consistency, and superficial treatment. If you have any, feel free
to
PM> offer them.
Haste to have the thing out asap, perhaps?
I'm not advocating "Learning Cocoa" (I haven't read it, what I've heard
of
it was not flattery, and that's a fact), but it's not *THAT* easy to
make a
good book (have you tried?), and it still might be *slightly* better to
offer
a questionable one now than a perfect one in the 2003.
---
Ondra Cada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
--__--__--
Message: 8
From: Ondra Cada <email@hidden>
Date: Thu, 23 Aug 2001 18:25:36 +0200
To: <email@hidden>
Subject: Re: Docs
Reply-To: email@hidden
Chuck,
Chuck Toporek (CT) wrote at Thu, 23 Aug 2001 11:03:45 -0400:
CT> ...trying to find a new author to work with me on a
CT> revision to make it better...
If it makes sense for you, I volunteer.
---
Ondra Cada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
--__--__--
Message: 9
From: Ondra Cada <email@hidden>
Date: Thu, 23 Aug 2001 18:25:05 +0200
To: <email@hidden>
Subject: Re: Docs
Reply-To: email@hidden
Chuck,
Chuck Toporek (CT) wrote at Thu, 23 Aug 2001 09:53:45 -0400:
CT> If that's the case, is there anyone here
CT> on this list (Ondra?) who might be interested in writing a "Cocoa
CT> Foundation Classes" book?
Why not? I wrote it already, actually ;), more a tutorial than a
reference
(but it seems to me the online docs are a great reference, just a bad
tutorial for newbies), and more a sequence of articles than a book, but
it
was regarded as a decent one here.
Well, what I wrote was in Czech. I'm *QUITE* willing to make a new,
better,
English release -- for a fair price. If you can support this part,
it's a
deal!
---
Ondra Cada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
--__--__--
Message: 10
Reply-To: "Todd Heberlein" <email@hidden>
From: "Todd Heberlein" <email@hidden>
To: "R. Tony Goold" <email@hidden>, <email@hidden>
Subject: Re: Docs
Date: Thu, 23 Aug 2001 09:31:59 -0700
Organization: Net Squared, Inc.
From: R. Tony Goold <email@hidden>
I'm inclined to agree with Searle. I see a lot of 'RTFM'
comments which seem inappropriate given the context,
Its appropriate. In this case it simply means
"Read The Forthcoming Manual"
I have to admit I am often surprised at how many descriptions for
methods are "forthcoming", and I do find that tends to discourage me
from looking. That is, the descriptions may be there, but I have hit so
many brickwalls in the past that I am hesitant to invest lots of time to
look for something.
However, I am not ready to blame Apple. The developers and tech writers
obviously have a lot on their plate, and they have to prioritize. Speed
and stability are two of my primary complaints. I hear lots of
grumbling by Carbon folks about the flux and stability of that side of
the house, and getting lots of MacOS 9.x apps ported to Carbon is
probably a very high business priority (or at least, it should be IMHO).
So for now I shall be patient. And I am thankful for this mailing list.
And I will try to never tell anyone to RTFM.
Cheers,
Todd
--__--__--
Message: 11
Date: Thu, 23 Aug 2001 12:30:33 -0400
From: Andrew Pinski <email@hidden>
Subject: Re: Passing variable argument list on to another function
Cc: "'Cocoa List'" <email@hidden>
To: Christian Mike <email@hidden>
Use vsnprintf instead of sprintf it is described in printf(3) man page.
Almost never use sprintf, use snprintf.
Thanks,
Andrew Pinski
On Thursday, August 23, 2001, at 12:15 PM, Christian Mike wrote:
As you have seen from previous e-mails, I am fighting a difference
between
NSString string formats and printf. I would like to do the following:
[myMutableString myAppendFormat:formatString,argList...];
and write my own function that essentially does:
-(void)myAppendFormat:(NSString *)formatString,...
{
char cString[1024];
va_list argList;
sprintf(cString,[formatString cString],argList);
[self appendString:[NSString stringWithCString:cString]];
}
But this doesn't seem to work quite right. How can I pass the variable
argument list portion of this on to sprintf?
Thanks.
Michael Christian
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
--__--__--
Message: 12
Date: Thu, 23 Aug 2001 08:34:19 -0700
Subject: Re: Bug in NSString stringWithFormat?
Cc: Cocoa Development <email@hidden>
To: Christian Mike <email@hidden>
From: "John C. Randolph" <email@hidden>
On Thursday, August 23, 2001, at 08:49 AM, Christian Mike wrote:
How do I make a request to Apple to make the
%[width][.prec]s
format specifier in NSString (and NSMutableString) work the same as
the C
printf function?
Perhaps something along the lines of:
va_list
args;
NSString
*properlyFormattedString;
char
*buf = alloca(someBigNumber);
sprintf(buf, format, args);
properlyFormattedString = [NSString stringWithCString:buf];
-jcr
"These kids today don't know the simple joy of saving four bytes of
page-0 memory on a 6502" - unknown
--__--__--
Message: 13
From: Ondra Cada <email@hidden>
Date: Thu, 23 Aug 2001 18:36:00 +0200
To: Christian Mike <email@hidden>, "'Cocoa List'"
<email@hidden>
Subject: Re: Passing variable argument list on to another function
Reply-To: email@hidden
Christian,
Ondra Cada (OC) wrote at Thu, 23 Aug 2001 18:34:48 +0200:
CM>> But this doesn't seem to work quite right. How can I pass the
variable
CM>> argument list portion of this on to sprintf?
OC>
OC> You can't. Use vsprintf instead.
And I forgot: be prepared that '%@' would not work (unless you
implement it
yourself, which is not *that* difficult)!
---
Ondra Cada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
--__--__--
Message: 14
From: Ondra Cada <email@hidden>
Date: Thu, 23 Aug 2001 18:34:48 +0200
To: Christian Mike <email@hidden>
Subject: Re: Passing variable argument list on to another function
Cc: "'Cocoa List'" <email@hidden>
Reply-To: email@hidden
Christian,
Christian Mike (CM) wrote at Thu, 23 Aug 2001 11:15:03 -0500:
CM> -(void)myAppendFormat:(NSString *)formatString,...
CM> {
CM> char cString[1024];
CM> va_list argList;
CM>
CM> sprintf(cString,[formatString cString],argList);
CM> [self appendString:[NSString stringWithCString:cString]];
CM> }
CM>
CM> But this doesn't seem to work quite right. How can I pass the
variable
CM> argument list portion of this on to sprintf?
You can't. Use vsprintf instead.
---
Ondra Cada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
--__--__--
Message: 15
Date: Thu, 23 Aug 2001 13:32:25 -0300
To: email@hidden
From: Rainer Brockerhoff <email@hidden>
Subject: RE: Bug in NSString stringWithFormat?
From: Christian Mike <email@hidden>
Date: Thu, 23 Aug 2001 10:49:51 -0500
How do I make a request to Apple to make the
%[width][.prec]s
format specifier in NSString (and NSMutableString) work the same as
the C
printf function?
I ran into this problem some weeks ago, and made a bug report.
NSString does this through CFString, so I also downloaded the source
files to Core Foundation ("CF-Lite") from the Darwin website, and found
the approximate place where this can be fixed... but there's so little
time...
...perhaps if someone submits the fixes to Darwin we'll get this in the
next version.
--
Rainer Brockerhoff <email@hidden>
Belo Horizonte, Brazil
"In the affairs of others even fools are wise
In their own business even sages err."
http://www.brockerhoff.net/ (updated July 2000)
--__--__--
Message: 16
Date: Thu, 23 Aug 2001 08:40:43 -0700
Subject: Re: Docs
Cc: <email@hidden>
To: Phillip Mills <email@hidden>
From: "John C. Randolph" <email@hidden>
On Thursday, August 23, 2001, at 09:10 AM, Phillip Mills wrote:
On 8/23/01 11:52 AM, "Chuck Toporek" <email@hidden> wrote:
I don't think we (or Apple) were trying to "Make Money Fast" by
publishing that book.
OK, I'll try to think of other reasons for the number of errors, lack
of
consistency, and superficial treatment. If you have any, feel free to
offer
them.
Oh, come on. It's superficial because it's an *introduction*. The
errors are due to the limited availability of cocoa developers to
proofread the book in their copious spare time while trying to get 10.0
out the door.
-jcr
begin
(If this message looks like it has an attachment, your mail reader is
brain-dead.)
--__--__--
Message: 17
Date: Thu, 23 Aug 2001 11:35:07 -0500
From: Jonathan Hendry <email@hidden>
To: <email@hidden>
Subject: Re: Docs
On Thursday, August 23, 2001, at 11:10 , Phillip Mills wrote:
On 8/23/01 11:52 AM, "Chuck Toporek" <email@hidden> wrote:
Phillip Mills wrote:
Even finding a person to type in the examples and verify that
they compile
would be a GIANT step in the right direction. I buy a lot of
O'Reilly
books, both for work and home. Obviouly, I usually like them or
I'd have
stopped years ago...but I feel like a sucker for having spent
money on this
one. It gives me the feeling that someone saw an opportunity to
"Make Money
Fast" and rushed it out the door with the least attention to
quality and
content possible.
I don't think we (or Apple) were trying to "Make Money Fast" by
publishing that book.
OK, I'll try to think of other reasons for the number of errors,
See their errata page. It's a book, not a webpage, they can't
change it dynamically.
lack of consistency, and superficial treatment.
Well, it _was_ called "Learning Cocoa", not "Mastering The AppKit
View System".
The preface states "For those who want to learn how to create Cocoa
applications, this book provides such a _starting point_."(Emphasis
mine)
It's a starting point. Not the ultimate reference to Cocoa that answers
all questions and explains everything.
"This book eases your way into the experience of Cocoa programming. It
encourages you to play, explore, and 'kick the tires'. When you finish
this book, you will be much better prepared to take on serious
application
development with Cocoa."
A book can't be everything to every person. It seems to me that the book
pretty well accomplishes what they set out to do. No, it doesn't
go into great depth about anything. It's only 300-some pages long,
and has to cover a _lot_ of topics, in a manner fit for beginners.
My OReilly book on Swing (just Swing) is twice as long. Why would
an in-depth look at _all_ of Cocoa be just 300 pages?
That's a nice, "can't we all just get along," thing to say and,
although I
seriouly applaud any efforts in that direction for the future, I
think you
should consider issuing a recall on the original. :-/
I think you wanted a different book. That doesn't mean this book
is broken.
Anyway, this is pretty much offtopic.
--__--__--
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
End of cocoa-dev Digest
Regards
Craig Morris
____________________
email@hidden
Home Ph. 03 64283100
Mobile 0417 319334