| README (107806) | README (112336) |
|---|---|
| 1/**************************************************************** 2Copyright (C) Lucent Technologies 1997 3All Rights Reserved 4 5Permission to use, copy, modify, and distribute this software and 6its documentation for any purpose and without fee is hereby 7granted, provided that the above copyright notice appear in all 8copies and that both that the copyright notice and this --- 58 unchanged lines hidden (view full) --- 67compilers on a variety of systems, but new systems or compilers 68may raise some new complaint; reports of difficulties are 69welcome. 70 71This also compiles with Visual C++ on all flavors of Windows, 72*if* you provide versions of popen and pclose. The file 73missing95.c contains versions that can be used to get started 74with, though the underlying support has mysterious properties, | 1/**************************************************************** 2Copyright (C) Lucent Technologies 1997 3All Rights Reserved 4 5Permission to use, copy, modify, and distribute this software and 6its documentation for any purpose and without fee is hereby 7granted, provided that the above copyright notice appear in all 8copies and that both that the copyright notice and this --- 58 unchanged lines hidden (view full) --- 67compilers on a variety of systems, but new systems or compilers 68may raise some new complaint; reports of difficulties are 69welcome. 70 71This also compiles with Visual C++ on all flavors of Windows, 72*if* you provide versions of popen and pclose. The file 73missing95.c contains versions that can be used to get started 74with, though the underlying support has mysterious properties, |
| 75the symptom of which can be truncated pipe output. Beware. 76The file makefile.win gives hints on how to proceed. | 75the symptom of which can be truncated pipe output. Beware. The 76file makefile.win gives hints on how to proceed; if you run 77vcvars32.bat, it will set up necessary paths and parameters so 78you can subsequently run nmake -f makefile.win. Beware also that 79when running on Windows under command.com, various quoting 80conventions are different from Unix systems: single quotes won't 81work around arguments, and various characters like % are 82interpreted within double quotes. |
| 77 78This compiles without change on Macintosh OS X using gcc and 79the standard developer tools. 80 81This is also said to compile on Macintosh OS 9 systems, using the 82file "buildmac" provided by Dan Allen (danallen@microsoft.com), 83to whom many thanks. 84 85The version of malloc that comes with some systems is sometimes 86astonishly slow. If awk seems slow, you might try fixing that. 87More generally, turning on optimization can significantly improve 88awk's speed, perhaps by 1/3 for highest levels. | 83 84This compiles without change on Macintosh OS X using gcc and 85the standard developer tools. 86 87This is also said to compile on Macintosh OS 9 systems, using the 88file "buildmac" provided by Dan Allen (danallen@microsoft.com), 89to whom many thanks. 90 91The version of malloc that comes with some systems is sometimes 92astonishly slow. If awk seems slow, you might try fixing that. 93More generally, turning on optimization can significantly improve 94awk's speed, perhaps by 1/3 for highest levels. |