home *** CD-ROM | disk | FTP | other *** search
- *************************************************************************
- ** **
- ** Known Bugs/Incompatibilities with MACIFY **
- ** **
- *************************************************************************
-
- (UNIX Version)
-
- + MACIFY will probably barf on non-text input/files (e.g. type special
- files, binaries, etc.)
-
- + MACIFY currently does not support wildcard extension. A future version
- will incorporate this, as well as allowing you to specify only the
- source filename, in which case the destination filename will auto-
- matically be named [sourcefile].conv.
-
- + If you give it a filename that does not exist, for input, MACIFY will
- most likely either complain or barf.
-
- + All error msgs and other such output are printed to stdout instead of
- stderr. If you're redirecting output to a file, and you hit an error,
- any messages printed will be dumped to the output file. This will be
- fixed in a later version.
-
- (Macintosh Version)
-
- + MACIFY will barf if the input file is non-text (i.e. application,
- binary, etc.)
-
- + MACIFY on the Mac WILL NOT work for converting Mac -> UNIX files.
- Therefore, I have disabled this menu item. Converting UNIX -> Mac,
- however, works fine. Please see the "README" file in the Mac dis-
- tribution for information about this bug. If you can fix it, please
- drop me an E-Mail notice telling what the problem is, and how to
- resolve it! Thanks!
-
- + MACIFY will overwrite the output file (file.out), if it exists
- already.
-
- + MACIFY curently doesn't support background events, and other such
- Mac-isms. This will perhaps be integrated in a future version.
-
- + The code for MACIFY is very messy.
-
- + MACIFY does almost NO error-checking. Thus, if you do something to it
- that it doesn't expect, it'll most likely bomb.
-