home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!charnel!rat!usc!sdd.hp.com!saimiri.primate.wisc.edu!copper!aspen.craycos.com!jrbd
- From: jrbd@craycos.com (James Davies)
- Newsgroups: comp.lang.fortran
- Subject: Re: Uglifier (was Re: Real Programmers)
- Keywords: n
- Message-ID: <1992Dec16.164347.21210@craycos.com>
- Date: 16 Dec 92 16:43:47 GMT
- References: <gay.724466320@sfu.ca> <1992Dec16.025109.24541@coe.montana.edu> <BzC6n8.J2G@news.cso.uiuc.edu>
- Organization: Cray Computer Corporation
- Lines: 23
-
- In article <BzC6n8.J2G@news.cso.uiuc.edu> ercolessi@uimrl3.mrl.uiuc.edu (furio ercolessi) writes:
- >
- >Hmmm ...
- >did any one ever made a source code uglifier, a filter removing
- >all comments, renaming all variables as A1,A2,... (*), removing all
- >extra spaces, replacing character constants with Holleriths, etc?
- >It could be a useful tool after all! Sometimes you do not want to
- >give away your sources, you would like to give only the binaries
- >but that's impractical ... this would be a brilliant intermediate
- >solution, give uglified code! :-)
-
- I once modified a prettyprinter I wrote to uglify instead (although I
- didn't go so far as to rename variables). Just removing the comments,
- randomly indenting, and randomly inserting spaces and continuation-line
- breaks has a remarkable negative effect on readability. Unfortunately,
- all of the things my obfuscator did (except for the comment removal)
- were reversible by using the prettyprinter.
-
- I've also used a simple C uglifier extensively for sending out proprietary
- source code in the past few years. (I haven't yet seen any of it posted on
- the net, so it must be working. :-) Of the two languages, obfuscated C
- has a stronger resemblance to transmission-line noise than obfuscated Fortran,
- probably because of all the curly braces...
-