6600pete@ucsbuxa.ucsb.edu (10/14/89)
Seems to me all this not-so-recent discussion of Pascal formatting is a bit... irrelevant. <dodging rotten vegetables> Somebody out there HAS a Pascal source formatter; I know it! And s/he probably even has the Pascal source! We could end all this formatting bickering if that person would just post the damn thing.
880716a@aucs.uucp (Dave Astels) (10/14/89)
In article <2526@hub.UUCP> pete@cavevax.ucsb.edu writes: >Somebody out there HAS a Pascal source formatter; I know it! And s/he >probably even has the Pascal source! Yes, I have one. I requested one from sources.wanted. I recieved a formatter designed for 'standard' (read old) Pascal. I have extended and modified it to handle various formatting styles and Turbo Pascal syntax (including TP 5.5). I have not completed modifications yet. >We could end all this formatting bickering if that person would just >post the damn thing. There are a couple of things I want to add before releasing it. There are MANY command line options. The defaults are hardcoded to my preferences, and I want to support a file of option settings that would be used automatically, or be overridden by a command line option. Hopefully I will get around to finishing it up soon, and then I will post it for furthur testing. -- - Dave Internet: 880716a@AcadiaU.CA Bitnet: 880716a@Acadia
ts@chyde.uwasa.fi (Timo Salmi LASK) (10/14/89)
In article <2526@hub.UUCP> pete@cavevax.ucsb.edu writes: >Seems to me all this not-so-recent discussion of Pascal formatting is >a bit... irrelevant. <dodging rotten vegetables> > >Somebody out there HAS a Pascal source formatter; I know it! And s/he >probably even has the Pascal source! > >We could end all this formatting bickering if that person would just >post the damn thing. In the case of Turbo Pascal, the Turbo Professional package has a source code formatter. But if it is anything to go by, standardization issues will not be resolved by formatters, because a good formatter has many options for alternative formats. So one would have to agree on the options. Thus we are back to square one. I do not want take sides in any bickering, but I think that a good point was made in reminding us that in large programming projects with several people involved formatting is an issue. This is natural, since formatting can be considered one aspect of documentation. ................................................................... Prof. Timo Salmi (Site 128.214.12.3) School of Business Studies, University of Vaasa, SF-65101, Finland Internet: ts@chyde.uwasa.fi Funet: vakk::salmi Bitnet: salmi@finfun
6600pete@ucsbuxa.ucsb.edu (10/15/89)
Firstly, let me apologize for not following standard context repetition; this emacs beast is defying my efforts. > ...standardization issues will not be resolved by formatters, > because a good formatter has many options for alternative formats. > So one would have to agree on the options. Thus we are back to > square one. Actually, we're FORWARD to square QUANTUM. The formatting problem goes away if you give everybody a formatter and let them run foreign code through it whenever they need to use that foreign code. Nobody's ever actually LOOKING at the same code, but then again group debugging over the phone is not recommended in the first place...
schwartz@psuvax1.cs.psu.edu (Scott Schwartz) (10/15/89)
In article <2526@hub.UUCP> 6600pete@ucsbuxa.ucsb.edu writes: | Somebody out there HAS a Pascal source formatter; I know it! And s/he | probably even has the Pascal source! | We could end all this formatting bickering if that person would just | post the damn thing. Anyone with access to Berkeley unix already has one: pxp. Since this was written at Berkeley, it is likely it doesn't have AT&T strings attached. Maybe the Berkeley csrg will be willing to include it with the rest of the free BSD sources. (It is written in C, though; part of the berkeley pascal compiler. Sorry!) -- Scott Schwartz <schwartz@shire.cs.psu.edu> Now back to our regularly scheduled programming....