Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 


Forgot your password?
Close
typodupeerror
×
Programming Books Media Businesses Book Reviews Apple IT Technology

Core Mac OS X and Unix Programming 212

Posted by timothy from the not-rotten dept.
Michael McCracken writes "Finally, a new OS X programming book that isn't just another introduction to Cocoa. This book adds a lot to the available references by covering the system as a flavor of Unix, presenting information on important topics like sockets, multithreading and pipes, which other OS X books leave out. It also includes coverage and sample code for some of the unfamiliar new technologies that have been introduced recently, such as the Keychain, Rendezvous (aka Zeroconf), and using the Security framework to authorize users." Read on for the rest of his review.
Core Mac OS X and Unix Programming
author Mark Dalrymple and Aaron Hillegass
pages 541
publisher Big Nerd Ranch
rating 9
reviewer Michael McCracken
ISBN 0974078506
summary A developer's guide to the Unix foundations of Mac OS X, including coverage of recently added technologies. Includes complete source code and online companion material.

If you've been learning Mac OS X Cocoa programming, you might already know Aaron Hillegass through his excellent book Cocoa Programming for Mac OS X, which was one of the first good introductory books on the topic, and is still one of the best available. Information about this earlier book can be found at bignerdranch.com/Book/. Both Aaron and Mark are instructors at the Big Nerd Ranch, which offers courses in Mac OS X programming. More information about them and the courses can be found at http://www.bignerdranch.com/Company/Who.html. This book is based on the course with the same name at the Big Nerd Ranch. The book's website and a link to order it online can be found at borkware.com/corebook/ . Discussion and further information for both books can be found at cocoadev.com/index.pl?CocoaBooks.

Audience and Writing Style

This book is not an introduction to programming on OS X. It doesn't explicitly cover how to use Apple's Project Builder or Interface Builder, or much of the Cocoa or Carbon APIs, except during discussion of code examples. So if you're entirely new to programming or to using Mac OS X, start with a different book such as Hillegass' earlier Cocoa Programming for Mac OS X to get up to speed with using the development environment. This book will leave you behind at times if you are unfamiliar with using the command line, however, the examples are complete enough to follow along by just typing in what's in the book.

Core Mac OS X and Unix Programming does have some very basic material in its first few chapters. They focus on the details of C programming, using the compiler, memory management, and debugging. These chapters will be mostly review for anyone who's developed in C on Unix before, but will be invaluable for programmers who learned to program using Java, for instance. They should also be required reading for programmers who started programming with Objective-C and Cocoa and are still unsure about using "plain" C. If you've ever complained about having to use a C API from CoreFoundation in your nice pure Cocoa application, don't avoid this book -- you need to read it even more.

The book is clearly written and easily understood. The writing is occasionally conversational, in keeping with its history as a course textbook. In the grand history of well-written technical books, it is also occasionally funny. The authors don't try to sell the technologies they discuss, instead giving practical advice that's useful to a programmer who is trying to actually build something. For example, the authors discuss bugs and inconsistencies in the system, clumsy API design and other problems that aren't great ad copy but you will need to know to develop robust applications.

I found this aspect of the book one of the most appealing, that it felt as though I was actually getting down to business. Gems of practical advice that can cut short frustrating problems appear throughout the book, so be sure to read carefully, don't just skim.

Hits

Here I'll discuss a few examples of where I think this book really shines. First, the level of detail of the standard Unix APIs and the development tools is excellent -- I learned many immediately useful things in the first 13 chapters. For example, chapter 8, "Debugging With GDB," was not simply a repeat of the online help, but also contained useful tips about how to use GDB more effectively, from using Objective-C specific features to tracking subtle memory errors. Programmers who had only used Project Builder's interface to GDB will benefit greatly from this chapter.

Next, there is pervasive sample code. Each chapter had a complete sample program demonstrating the topic at hand. Much of this code is also available online: see "Online Supplements" below.

Finally, as I mentioned before, the text contains tips and reminders throughout about potential mistakes, tricky problems, and differences between Mac OS X, OS 9, and other Unix flavors. A particularly useful example of this is in chapter 24, "CVS." There is a small but important paragraph that discusses using CVS 1.11 (as used in Sourceforge) with Interface Builder .nib files that can really save some grief. In other chapters, they even include workarounds for system bugs in some of the sample code. This pragmatic approach is really appealing.

Misses

In this section I'll mention a couple potential disappointments. You will have to be willing to learn by just reading code at times. Most of the code examples are not explained line-by-line as is the custom in tutorial books. Comments explain tricky code, and the text covers the areas most relevant to the chapter topic, but for other sections, understanding is up to you. I mentioned this because although I feel the code is clear and a fair trade-off was made to fit in a lot of information, the amount of explanation you like is a matter of personal preference, and so you should know what to expect.

Pointers to further reading is another problem. Aside from referring to man pages, there is little attempt to point to good external documentation on any of the more complicated topics. One chapter is not enough to completely cover BSD Sockets, for example, and so a reference to a Unix network programming book would be useful. In fact, every chapter could be improved by a references section, even if it only collected links to Apple online documentation or Unix community websites. With all the practical knowledge in this book, the lack of clues on where to look to answer your own questions was disappointing.

Finally, the cost of the book, at $97.95, is higher than you might expect. I admit that as a student, I would have to think twice about paying this price, although I am sure it would be easily justifiable for professional programmers. I believe that it is worth the price, however, because you would have to buy several other books to cover the same range of topics, and you still wouldn't get the Mac OS X specific information.

Online Supplements

The authors have set up a promising resource for the book at http://borkware.com/corebook/ . The site includes the sample code, errata, reader comments indexed by the chapter and topic they refer to, and a general discussion board. There are already some errors listed, and a few pointers to useful documentation and interesting external discussions on mailing lists. The sample code is not complete at the time of this review, but more is being added. This site looks like it will be a useful addition to the book, especially if many good chapter-indexed comments are added. The site could be kept open as a reading companion while going over a chapter in the book. This site's organization is, in my opinion, much more useful and usable than other books' companion websites, including the site for "Cocoa Progamming," which hid its information from you unless you knew which page number was relevant to your topic.

Conclusion

Core Mac OS X and Unix Programming is a very useful book, and even if you've been developing on Unix systems for years, you can probably learn a few immediately useful things by reading it. I recommend it for any serious Mac OS X programmer who wants to know what to read next after all the tutorials that have come out in the last year or so. I suspect it'll become a canonical reference, and may even be in need of a clever nickname. Congratulations to Mark and Aaron on a job well done.

Michael McCracken is a grad student and Mac OS X developer; he says "I have not attended any Big Nerd Ranch courses, nor have I met either author, although I did see Aaron Hillegass in a crowd once." Update: 07/02 17:36 GMT by T : According to publisher AtlasBooks, bn.com won't actually be carrying this book, but you can get it right now from Atlas. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
This discussion has been archived. No new comments can be posted.

Core Mac OS X and Unix Programming More

Core Mac OS X and Unix Programming

Comments Filter:

  • Whoa (Score:5, Funny)

    by Anonymous Coward on Wednesday July 02, 2003 @11:02AM (#6350343)
    Be careful, you might actually teach them some good programming techniques.

  • Microsoft port (Score:2, Interesting)

    by SolidGold ( 86023 )
    It is interesting to note that Microsoft in a previous article said that they had no intention of porting Office to Linux right now, but being that they have ported it to OS X most of the work has already been done.

    • Re:Microsoft port (Score:3, Insightful)

      by christurkel ( 520220 )
      It would think its closer to a FreeBSD port with you port to Mac OS X. I could be wrong, however.

    • Re:Microsoft port (Score:5, Informative)

      by Halo1 ( 136547 ) on Wednesday July 02, 2003 @11:13AM (#6350477)
      MS Office is a Carbon app. There's no carbonlib for any *nix except Mac OS X out there. Porting it to Linux would mean either porting carbonlib (i.e. a cleaned up version of the legacy Mac OS api + extensions) to Linux, or rewriting it from the ground up (just like the Mac OS X version is almost a complete rewrite compared to the Windows version).

      • Re:Microsoft port (Score:4, Informative)

        by Anonymous Coward on Wednesday July 02, 2003 @01:25PM (#6351701)
        Worse than just a Carbon app. MS Office for Mac is written using WLM (Windows Compatibility Layer for Mac - pronounced "will am"). This was Microsoft's idea for single sourcing office for Mac and Windows back in the early 90s.

        They have long since given up the single source idea. The Mac BU has their own copy of Office Source. However, it is still written using bastardized Windows API on top of a Carbonized WLM.

        The whole thing is a mess. There is basically a zero chance that they are going to pick that up and port it to Linux. If they decided they wanted to port it to Linux, they would be better off buying something like ThinkFree Office to be the basis of the port (for several reasons). In fact, *if* they were going to port to Linux, they'd probably do just that.

        I used to be a Mac developer there.
      • MS Office is a Carbon app. There's no carbonlib for any *nix except Mac OS X out there. Porting it to Linux would mean either porting carbonlib (i.e. a cleaned up version of the legacy Mac OS api + extensions) to Linux,

        Wait a minute - if I had my modpoints now, I'd surely give you an "insightful" just for this. Are there any attempts to create something like free carbonlib compatibility environment? This could bring much more than just MS Office to Linux and other free OS'es. After all, majority of games
        • Just porting carbonlib wouldn't cut it in most cases. Almost all Mac apps also use Quicktime. For sound, they sometimes use CoreAudio under Mac OS X. Most games use the HID Manager for input... So I'm not sure whether just carbonlib would help a lot.
    • Yes but have you ever used MS office on OSX, it is slow and incredibly buggy (jokes about microsoft aside office on XP is rock solid) and that's with standard hardware and a fast RISC processor to work on, imagine what it would be like under Linux with all sorts of random hardware thrown in there. The real reason they won't port office to Linux however, isn't about speed or reliability but simply because Office on Linux just wouldn't sell. Most Linux users realise that there are good free alternatives lik
      • "The real reason they won't port office to Linux however, isn't about speed or reliability but simply because Office on Linux just wouldn't sell."

        It would sell more than you think. For companies that want to move the corporate desktop over to GNU/Linux but feel that OpenOffice and the other alternatives aren't fit, it would sell like hotcakes.
        • Why would MS port Office to a platform they see as competition for Windows? Apple isn't competition; Office on the Mac doesn't take away potential sales of Windows and other MS products. Selling Office for Linux, on the other hand, would just encourage migration from Windows to Linux.
        • Ah yes, but everyone wants to pay OOo prices don't they ;-)

          Most equate open aource to being free of charge. To quote other /. posters; "Joe Sixpack just wouldn't understand."

      • Re:Microsoft port (Score:3, Insightful)

        by Anonymous Coward
        I would think that porting Office to Linux would validate the platform, it would be a message from Microsoft that they believe enough in Linux to support it. Porting Office would allow even more people to switch FROM Windows; and that would be the start of Micrsoft loosing control.
        • Oracle has already "validated" the platform, as has Sybase, etc. MS will move to Linux kicking and screaming the same way they were brought to the Internet. Heh, I wonder if when that happens MS will claim to have invented Linux the same way they did the Internet.
      • actually I have office for OS X and it actually seems to run fine ... very well if you consider I have 466 G3 ibook.

      • Re:Microsoft port (Score:3, Informative)

        by jeremyp ( 130771 )
        I use it every day. With the current patch level (10.1.3) it's not slow (any more so than any other OS X app) and it's not buggy - well I've not seen any.

      • Re:Microsoft port (Score:3, Insightful)

        by Mr. Show ( 648023 )
        The real reason they won't port office to Linux however, isn't about speed or reliability but simply because Office on Linux just wouldn't sell.

        Microsoft has an effective monopoly in two areas: operating systems and office software. They are also the only two divisions within Microsoft that are profitable, and support all of their other ventures into PDAs, game consoles, set top boxes, smartphones, and on and on. Office on Linux might not sell to college kid hackers running Linux on their Alienware machi
    • Ehm. Native OS X (Cocoa) apps really aren't very close to Linux apps. First of all, they're written in Objective-C, and that'd make it *harder* to properly integrate stuff in GNOME or KDE, I think. But most importantly, the Office ports for OS X use the whole NS (NextStep) framework Apple developers use. There is no way you'll get that ported to GNU/Linux (closed source), which means you either have to use a replacement that hardly works correctly, like GNUStep, or you'll have to build your own libraries. I
      • Just read Office for X is a Carbon app, not a Cocoa one. Sorry, but I've never used Office for Mac (thank God). Same still goes, only for Carbon, though.
    • M$ doesn't have a whole lot to fear from Mac OS X because it *only* runs on PPC.

      But if they developed Office for x86 Linux, Linux popularity on the destkop would rise enough to hurt Windows sales.
    • It's not a port. It's a completely different product. They tried a direct port with Word 6, and it failed miserably. Mac users don't want Windows ports.

      Most of the work is most certainly not done. It's not like we run /usr/bin/word. It's a Cocoa app, not a UNIX app.

    • Re:Microsoft port (Score:5, Interesting)

      by Graff ( 532189 ) on Wednesday July 02, 2003 @11:25AM (#6350609)
      Microsoft in a previous article said that they had no intention of porting Office to Linux right now, but being that they have ported it to OS X most of the work has already been done.

      Actually that's not quite true. Microsoft programmed Office for the Mac using the Carbon API and libraries which are part of MacOS. This is a set of APIs which are completely proprietary to MacOS and which bring a program no closer to Linux than a program which uses the Windows API program does.

      The only way in which doing a MacOS port of a program brings it closer to doing a Linux port is most programmers doing a port tend to separate out the parts of the program which rely on a particular operating system from the parts that are platform-agnostic. Thus you will most likely end up with a large chunk of the code which can be re-used to add a front end for any particular system type. This is not a requirement for a port however, it is just smart programming. In fact, it is even smarter programming to do this in the first place. Microsoft may or may not have done this, but I'm doubting that they did. From what I understand they basically program the Mac versions of their programs from nearly the ground up.

      In programming the Myth series of games, it was often said by the developers at Bungie that the platform-agnostic parts of the games took up about 90% of the code, while each port took up 10% more. So for a 10% investment in additional coding you could sell the game to a another platform. This requires a bit of planning but it is a much better way to program than to do one version for one platform and then have to completely redo you work to get it to run on another. Finally, there is another great advantage to doing multi-platform programming. Often a bug which doesn't show on one platform will show up on another, allowing you to clean up any possible problems before they get you into trouble later on.
      • This is a set of APIs which are completely proprietary to MacOS and which bring a program no closer to Linux than a program which uses the Windows API program does.

        Actually, a program using Windows APIs is much closer to Linux because of winelib.
    • PCODE on Linux, YAYYY!!!

      Jokes aside, how much PCODE is still left in Mickeysoft products?
    • how the fuck do these "it runs on MacOSX so it could run on linux" posts get moderated up?

      Last time I checked, MS Office, QuickTime, PhotoShop, et alia were not command-line only, posix-only applications.

      Anyhow, shouldn't you be spouting that gimp, open office, and mozilla are better applications?

  • keychain (Score:3, Informative)

    by el stevo ( 580437 ) <edibleplastycNO@SPAMyahoo.com> on Wednesday July 02, 2003 @11:06AM (#6350385)
    keychain has been a part of the mac os since OS 8, albeit not it it's current unix-ized form

  • C'mon! (Score:4, Funny)

    by Anonymous Coward on Wednesday July 02, 2003 @11:08AM (#6350405)

    You can't be "unfamiliar with the command line" and a programmer. Pick one.

    • Re:C'mon! (Score:2, Insightful)

      by Anonymous Coward
      Sure you can. Mac people haven't needed a "command line." Converts from Windows don't need one either. I'm a professional Windows programmer, and I don't use the command line.

      • Re:C'mon! (Score:3, Interesting)

        by bladernr ( 683269 )
        I have found the command-line essential, even when programming Windows. Even though the Mac (a system I have never been a developer on, but may learn) has a terrific UI, leaving out the command-line would be a mistake, and the author was right to include that content.

        When programmers are beginning, it is easy to avoid the command-line altogether, since their projects are probably simpler. I imagine that the author's previous books on introductory topics focused on the GUI.

        I am a software professional as w

        • No matter how good the tools, you can never escape from the command-line for complex systems.

          Agreed.

          I work for a company that makes "enterprise" client-server apps, and out customers demand we have a complete command-line interface, along with a standard GUI and an API interface. All interfaces are actually running the same client commands, so we have some kind of interface parity. (No, our GUI is not a wrapper around the CLI! The "client" is abstract, and can only be accessed via your choice of inte

          • For now, anyway. Maybe when all the old-timers die (hmm, I wonder if this means me, as well), the CLI will die.

            I don't think this will be the case. I, while not an old-timer @ 23 years, love the CLI. I continue to see a need for both. I use both, and use them when they should be used. The CLI is great for scripting and such, and can be indispensable when speed is important. Sure, the CLI has a steeper learning curve, but once you get to know the commands, options, etc., most people favor the command
          • Saying that the CLI would die when the old timers die because of the GUI is like saying books will disappear when those folks from before TVs die off. Each has their place.

            Now I think that in some ways Apple is still a little too dependent upon the CLI in OSX. Lots of things don't have a GUI that should. But that doesn't mean the CLI isn't welcome. After Sys9, having a full sophisticated CLI is a dream. Further with Applescript integrating the two is possible in a way not dreamt of in Windows or Linu

    • You can't be "unfamiliar with the command line" and a programmer. Pick one.


      Well, I suppose you could write VB code, but calling that programming is quite a stretch.

    • Sure you can, if you're a VB coder or something. (Yeah, I know, contradiction in terms...)

    • Re:C'mon! (Score:3, Insightful)

      by Snocone ( 158524 )
      You can't be "unfamiliar with the command line" and a programmer.

      Then what do you call those things that ran on Mac OS X and the people who wrote them, if they weren't "programs" and "programmers" respectively? Took me 16 years of shipping commercial software products before I had to use a command line at all, personally.
      • <QUOTED TEXT>

        You can't be "unfamiliar with the command line" and a programmer.

        Then what do you call those things that ran on Mac OS X and the people who wrote them, if they weren't "programs" and "programmers" respectively? Took me 16 years of shipping commercial software products before I had to use a command line at all, personally.

        </QUOTED TEXT>

        Hmm. 16 years. Commercial software. Let's see, that would (assuming the first time was five minutes before your post) put you at 1987, not usi

        • put you at 1987,

          '85, actually.

          assuming you were a DOS programmer

          Nope, just Mac.

          on the Mac, your choices were - Mac Pascal or MPW

          Au contraire!

          Started out in MacFORTH, then Consulair C, then THINK (later Symantec) Pascal and C, then CodeWarrior. Never touched Mac Pascal ever, and only extremely rarely had anything to do with MPW -- certainly not enough to be any reasonable definition of "familiar" with it.

          Heck, I wouldn't even call myself "familiar" with the OS X command line yet ... a 'power user

  • $97.95?! (Score:5, Funny)

    by yumyum ( 168683 ) on Wednesday July 02, 2003 @11:08AM (#6350413)
    That'd put a major dent in my crack usage...

  • Aaron Hillegass as an instructor (Score:5, Informative)

    by blakespot ( 213991 ) on Wednesday July 02, 2003 @11:12AM (#6350462) Homepage
    I am approaching the end of Aaron's previous book, Cocoa Programming for Mac OS X, and can say that throughout, it's as though he is sitting there beside you, casually instructing you as you move through the work. An excellent introduction to Cocoa, it has given me a fairly solid graps of the concepts that make up Cocoa development (which began in the late 80's with NeXT) and I have made some real strides on my own, veering from the courework in the book. Goes far beyond some of Apple's cryptic guides I've encountered.

    Oh...and do yourself a FAVOR and download Cocoa Browser [nifty.com] before you even lay down a single line of Objective-C. The ONLY way to access the frameworks references.

    blakespot

    • AppKiDo (Score:2, Informative)

      by hayne ( 545353 )
      do yourself a FAVOR and download Cocoa Browser before you even lay down a single line of Objective-C. The ONLY way to access the frameworks references.

      I much prefer AppKiDo [mac.com] since it allows searching and it shows you a list of all methods of a class (including those from super classes) as well as a list of just those provided by the class itself.

    • "It's as though he is sitting there beside you, casually instructing you as you move through the work."

      That's gonna make it harder to code in the nude ...

  • Just wondering... (Score:5, Interesting)

    by rampant mac ( 561036 ) on Wednesday July 02, 2003 @11:12AM (#6350464)
    Those WWDC people who have access to Apple's upcoming OS, Panther...

    How relevant will this information be with Panther merging to BSD 5.0 userland and the new Xoode environment?

    I can't seem to justify the price for this book ... yet.

    • Re:Just wondering... (Score:3, Interesting)

      by markd ( 36343 )
      From what I saw at WWDC, only a couple minor points here and there will need to be updated (like the new exception mechanism in objective-C replacing the setjmp/longjmp one that currently exists). The tech addressed by this book is more at the plumbing level which doesn't change a whole lot release to release. We don't dwell a lot on the IDE, figuring that folks will know what they're doing in their IDE of choice. (I personally use emacs for my day-to-day work)

    • Re:Just wondering... (Score:2, Insightful)

      by Anonymous Coward
      I bought it anyway. Sure, Panther will change things, but there is still a lot of stuff in there. I'm still using Aaron's Cocoa book despite many changes to Project Builder that can sometimes make it difficult to follow the examples. I expect the same of Xcode. Much of the book is good reference for things that I've seen before as a Unix C programmer, but forget because I don't look at them every day.

      It's expensive. Very expensive. With my current budget situation, I had to figure out what else I wasn't go

  • Confused (Score:4, Funny)

    by Anonymous Coward on Wednesday July 02, 2003 @11:18AM (#6350536)
    I see Unix in the title but there is no mention of SCO. Just what in the hell is going on around here?
    • I see Unix in the title but there is no mention of SCO. Just what in the hell is going on around here?

      SCO was too busy imagining a beowolf cluster of these.

  • Good News... (Score:4, Informative)

    by DoctorPepper ( 92269 ) on Wednesday July 02, 2003 @11:25AM (#6350619)
    ... If you have a Barnes & Nobel reader's advantage card:

    List Price: $97.95
    Our Price: $78.36
    You Save: $19.59 (20%)

    Readers' Advantage Price: $74.44

    (OUCH!) This looks to be one book I'm going to have to skip. Bummer.

  • Wrong URL to Buy the Book (Score:3, Informative)

    by BigNerdChris ( 686207 ) on Wednesday July 02, 2003 @11:33AM (#6350696)
    You can't (currently) get the book at bn.com. Use this web page to buy the book: http://www.atlasbooks.com/marktplc/00981.htm [atlasbooks.com]
    • I ordered mine from Atlas Books a few days ago for $102.95 with shipping. At that time I could not find it at Amazon. The price is a bit steep but it's less than the $3500 for the class.
  • will they sue these guys for having Unix as part of the Book title?

  • the price (Score:2, Informative)

    by Anonymous Coward
    I plan on buying this book when I get the cash, but from talking to Aaron last week at WWDC, the price is that high is because it's basically the course material for the classes they have at the Big Nerd Ranch. Of course...I can't afford the classes, so I'm going to get the book.
  • Am I reading it correctly that the price is $US97 plus shipping?
    Also, is it showing up on Amazon? I looked and didn't see it.
    Clues gratefully accepted...

  • Weird Times (Score:3)

    by SomeOtherGuy ( 179082 ) on Wednesday July 02, 2003 @02:26PM (#6352227) Journal
    I know OS X is all unix central nowadays...Yet to see a book about core Unix programming on a Mac still has me to a doubletake the same if I saw a book called "A vegetarians guide to cooking steak."

  • I know that GNUStep is implemented in Obj-C, but would this book be useful for learning Obj-C and the GNUStep interface? Would there be any advantages for doing so (would I gain any cross-platform Linux-Mac OS X benefits)?
    • I know that GNUStep is implemented in Obj-C, but would this book be useful for learning Obj-C and the GNUStep interface?

      I haven't read it but judging from the title and review, I don't think it will do you much good right now. It appears to be talking about some of Apple's own custom frameworks and lower level UNIX stuff. Somebody on the GNUstep list mentioned recently that they're interested in cloning Rendezvous but it's still just vapor.

      Now, Aaron Hillegass' previous book, Cocoa Programming for Mac OS

  • This is indeed a useful book. As someone who is a long time Unix programmer and just starting out with Objective C and Cocoa I found it mostly above my head but a book I know I will grow into and find useful for a long time.

    I agree with the reviewer about the lack of pointers for further info. I hope that the authors might fix this at the excellent site for the book.

    For close to $100 this is an expensive book, but if you want to learn to write professional Mac apps then it's probably worth the price. Th

Slashdot Top Deals

Don't tell me how hard you work. Tell me how much you get done. -- James J. Ling

Close