home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.bbs.waffle
- Path: sparky!uunet!spool.mu.edu!uwm.edu!psuvax1!atlantis.psu.edu!barr
- From: barr@pop.psu.edu (David Barr)
- Subject: Re: The woes of ^Z
- Message-ID: <pei1Hf4hrb@atlantis.psu.edu>
- Sender: news@atlantis.psu.edu (Usenet)
- Organization: Penn State Population Research Institute
- References: <28Dec92234255@miracle.com> <miXLwB1w165w@1776.COM>
- Date: Wed, 30 Dec 92 21:28:41 GMT
- Lines: 26
-
- In article <miXLwB1w165w@1776.COM> bob@1776.COM (Robert Coe) writes:
- >phil@miracle.com (Phil Hill) writes:
- >> The most important argument is that **WAFFLE** doesn't treat ^Z's the same
- >> when run on a UNIX system. It is important that Waffle remain compatible
- >> with itself. Or to at least document the difference.
- >
- >But *UNIX* doesn't treat ^Zs the same way as MD-DOS does. (It doesn't treat
- >file names the same either. Should Unix Waffle refuse to respond to file
- >names that would be illegal in MS-DOS?) Should Waffle be "compatible with
- >itself" or should it try to blend in as much as possible with the environment
- >in which it's run?
-
- I agree whole-heartedly. Phil, you're off your rocker. Waffle
- should not have to "be compatable with itself". Such a philosophy forces
- you to stoop to the lowest common denomenator of features for an application.
- It's just plain dumb.
-
- The solution for the ^Z problem in Waffle is to not put a ^Z in
- DOS text file. You're asking for trouble anyway. Tom, it's not worth fixing
- in Waffle unless you have some spare time to write your own DOS text I/O
- routines.
-
- --Dave
- --
- System Administrator, Population Research Institute barr@pop.psu.edu
- What if there was no such thing as a hypothetical question?
-