Eformat V1.4 Documentation Legal stuff, I guess. I make no warranties as to what this software will or will not successfully do. I take no liability for any damage it does. In other words, if it screws up your source, it's not my fault. This Program is Freely Distributable Sourceware. That means, if you like the program and use it, send me some of your source, in E. (Which is what this program was written in!). If you're not an E programmer, send me one of: Brand new *nix RPG port, Brand new Strategy/Tactical/Empire game, cool mods/samples or finally, a registered version of your software and I'll return the favor. For those of you who don't know what E is, I'll plug it for you. E is a very nice, fast, small language that allows you to easily do pretty much anything C can do, but doesn't take up 40 megs of HD space and an 030. In fact, E is running on my 2 floppy, 2 meg A1200 right now and compiling damn fast (With no swaps, I might add). The latest version of E is version 2.1b, by Wouter Van Oortmerson.(sp?), Thanks Wouter! Hurry up with 3.0! Addresses: Email: ao443@freenet.carleton.ca (Nyx didn't pan out, sorry.) Fido: 1:140/58 Snail Mail: Jason Maskell #5, 409 Main Street E. Saskatoon,Sk S7M 1h2 Also, look for me on the E mailing list! To subscribe, send email to amigae-request@bkhouse.cts.com, with SUBSCRIBE AmigaE . The program itself: Very, very simple program I wrote for myself to clean up all that horribly messy example source that comes with E. Usage is as such: eformat >ram:whatever messysource.e The redirection is the only way you'll get the output into a file. I could've done it with a source file name, but then it would've taken me some time to write, instead of the 3 or 4 hours it did. I've put some more refinements in since then, and any E programmers may feel free to steal stuff from it. Eformat will properly nest all control structures, IFs, SELECTs, etc.. Try it, and as Wouter says, feel the power! Known bugs and history: V1.0 Unfortunately, Eformat does not correctly format it's own source. The reason is because it's not truely parsing the code in a really smart manner, so if somebody is REALLY REALLY messy, it probably won't work correctly. I may fix this in the future. (Yah, and pigs could fly.) No, really, it could happen! V1.1 Version 1.0 had some stupid bugs in it that I missed. Fixed were: -Eformat now properly does SELECTs, nested or otherwise. -Got rid of the silly Raise error handling I was using and went back to what I know. -Fixed some cosmetic errors. V1.2 In getting rid of the stupid bugs in v1.0, I stupidly left the debug stuff in v1.1, rendering the program rather corrupting. This has been removed. Any E programmer would've spotted this (and fixed it) anyway. V1.3 (Jan 25th 1994) Eformat now properly formats itself! V1.4 (Feb 9th 1994) Had some complaints about Eformat guruing, and fixed the problem by using the stack code included in the E source archive. Eformat also wasn't properly formatting some WouterCode. Problem is now fixed, Eformat is quite a bit more robust than it used to be. Fixed some cosmetic stuff. (Resolved to test it a little better in the future!) What wasn't fixed: Still doesn't parse code in an intelligent manner, so really messy code, (like, say, Wouter's), will still be somewhat messy. And finally, if anyone has any suggestions for this program, feel free to relay them. I didn't include any kind of point and click WB interface because I don't really consider it neccesary. Doesn't every real programmer know how to use a shell? Jason Maskell Feb. 9th 1994