Path: utzoo!utgpu!watmath!att!pacbell!ames!xanth!mcnc!rti!sunpix!matthew
From: matthew@sunpix.UUCP ( Sun Visualization Products)
Newsgroups: comp.sys.apple
Subject: Re: NuARC v2.00 (Apple //gs APW NuFX Archive Utility)
Keywords: Interesting....
Message-ID: <746@greens.UUCP>
Date: 7 Aug 89 21:15:26 GMT
Organization: Sun Microsystems, Research Triangle Park, NC
Lines: 54

Andy Mcfadden has recently posted 'NuARC v2.00' to comp.binaries.apple2.
Since comp.binaries.apple2 does not have a discussion subgroup, and I've
never been successful e-mailing thru cory.Berkeley.EDU, I'm starting this
dicussion here.

First I don't own an Apple //gs (only an Apple ][plus, Apple //c and 
Apple ///), but I do find the program interesting and do have a comment
on the choice of options.

Here's the options list as per the comp.binaries.apple2 posting.


	Usage: nuarc option archive-name [filenames]
	Option must be one of:
	  a - add to archive [v2.0 - uncompressed only]
	  b - unpack/unsqueeze from Binary II archive [v2.0 - not yet]
	  c - create archive (add, but suppress 'create' message)
	  d - delete file from archive
	  f - freshen files in archive [v2.0 - not implemented]
	  i - verify archive integrity [v2.0 - read file, check CRCs]
	  m - move files to archive (add, delete original)
	  t - display table of contents (list filenames only)
	  u - update files in archive [v2.0 - not implemented]
	  v - verbose listing (ProDOS 8 ShrinkIt listing)
	  w - who did what (credit where due, licensing info)
	  x,e - extract from archive [v2.0 - uncompressed only]
	  z - dump all known info about an archive
	
	Type 'nuarc w' for license and author information.
	

The chosen options appear similar to ARC and ZOO options, but a few changes
are going to make people confused.

First:	't' is the option used to 'test' the intergrity of archives under
	ARC and ZOO. I recommend it be used under NuARC also.

Second:	'l' is the option to 'list' the contents of an archive.

Third:	'h' is typically the option used to request the usage page. I've
	scene some software where a test for the 'h' option was in the code
	and it called up the 'usage' message.  Other times it was omitted
	and any invalid option display showed the 'usage' message. (Result:
	a 'program -h' still displayed the 'usage' message.)

Fourth:	A question.  What is the difference between 'a' and 'c'?  Is 'c' 
	really needed?


-- 
Matthew Lee Stier                            |
Sun Microsystems ---  RTP, NC  27709-3447    |     "Wisconsin   Escapee"
uucp:  sun!mstier or mcnc!rti!sunpix!matthew |
phone: (919) 469-8300 fax: (919) 460-8355    |