Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!necntc!rayssd!unisec!mark From: mark@unisec.UUCP Newsgroups: comp.sys.amiga Subject: Re: Text file tab utility Message-ID: <444@unisec.USI.COM> Date: Wed, 25-Mar-87 08:52:06 EST Article-I.D.: unisec.444 Posted: Wed Mar 25 08:52:06 1987 Date-Received: Sat, 28-Mar-87 00:44:47 EST References: <443@unisec.USI.COM> <1814@vax135.UUCP> Distribution: comp Organization: UniSecure Systems, Inc. Newport, R.I. Lines: 52 Summary: Detabbing print utility for tabs < 8 In article <1814@vax135.UUCP>, cjp@vax135.UUCP (Charles Poirier) writes: > In article <443@unisec.USI.COM> mark@unisec.USI.COM (Mark Rinfret) writes: > >(right?). Finally, I have Z which, for all its faults, allows me to set > >tabs where I want them (4) and stores true tab characters in the file. > > Well for my money, I like Z a lot but the tabs handliing is one thing > ... > ... , but it is imperative that I be able to set 4-wide > indentation stops that *print* *out* *on* *my* *printer* as 4-wide. My > printer has only 8-space tabs and it does not auto-wrap. A major point > of 4-spaces indentation is that I can more easily read deeply nested > code. I hear you! One of the first things I did when I started developing code on the Amiga was to get a "detabbing print utility" (expands tabs) and customize it for my own use. The command line takes an option (-i) which allows you to specify what your tab setting is. I've also added Unix-style wildcarding (via Aztec's "scdir" function). It (pr) also outputs an optional header with filename, date, page number and the line number of the first line on the page. My reason for posting this rather than sending e-mail is to get some response/opinion to a concern related to "public domain" software. Just for fun, I added a copy of C. Heath's "getfile" requester package so that you can call my "pr" without filename parameters and it will put up a requester (it currently only works for one file, but I could easily add a "more?" loop to it). Here's the rub - I modified the "getfile" package to return a status code which informs me when the CANCEL gadget has been clicked. The author explicitly states in his source that no modified version of this package is to be released without clearing it through him (though it is on the update disks for the Aztec C compiler and probably a thousand other BBS's, etc.). I have so far respected the author's wishes, but I have no desire to send a letter out into the void, waiting for "permission" to re-release the modified source. What I'm leading up to is this - would it be ethical for me to maintain opening credits to C. Heath but rename the modified routine? I've been hesitant to do this since I don't want to step on any toes. I could just release the source (just another dumb little tool, mind you) with pointers to the changes that must be made, but that's a hassle. When I put things in the public domain (not much for Amiga yet, much for C64), I wave goodbye and encourage the world to do with it as they will. Though I am grateful to C. Heath for releasing his code in the first place, I wish he had been less restrictive in his "conditions". Thanks for listening. Mark -- | Mark R. Rinfret, SofTech, Inc. mark@unisec.usi.com | | Guest of UniSecure Systems, Inc., Newport, RI | | UUCP: {gatech|mirror|cbosgd|uiucdcs|ihnp4}!rayssd!unisec!mark | | work: (401)-849-4174 home: (401)-846-7639 |