1*58349Sbostic# @(#)README 5.2 (Berkeley) 03/01/93 258344Sbostic 358344SbosticFor compiling: 458344Sbostic There are several flag options for compiling 'ed' into executable. 558344Sbostic 658344SbosticThis table briefly describes the flags used in compilation: 758344Sbostic 8*58349Sbostic BSD | POSIX 958344Sbostic specifies over-riding behaviour in historical terms: 1058344Sbostic BSD=> BSD behaviour when confilicting with P1003.2, 11*58349Sbostic POSIX=> as P1003.2 specified when conflicting with BSD. 1258344Sbostic 13*58349Sbostic STDIO | DBI | MEMORY 1458344Sbostic specifies which method is to be used for the buffer. 1558344Sbostic Be sure to understand that there are trade-offs with 1658344Sbostic any of the methods: 1758344Sbostic STDIO=> standard I/O temp file, 18*58349Sbostic DBI=> BSD recno database file (db(3)), 1958344Sbostic MEMORY=> ye olde silicon. 2058344Sbostic 21*58349Sbostic One of each compile flag option _must_ be chosen to get a sensible 22*58349Sbostic compile. 2358344Sbostic 2458344SbosticOne define not listed above, yet used as a flag, is RE_STARTEND. This 2558344Sbosticis used to automagically check if you are using the real BSD RE interfaces. 26*58349SbosticSee regex(3) (4.4BSD) for a description of RE_STARTEND; an extension to 2758344SbosticP1003.2 B.5. If you happen to be using another POSIX regex(3) this 2858344Sbosticautomatically taken care of; the old RE interfaces are unsupported. 2958344Sbostic 3058344SbosticThis implementation of `ed' is a superset of the POSIX 1003.2 description 3158344Sbosticfor `ed' to remain compatible with earlier (BSD) versions of `ed'. 3258344SbosticHence, any BSD 'ed'isms that do not conflict with P1003.2 are available 3358344Sbosticto the user even under the POSIX flag compilation. Likewise, any POSIX 3458344Sbostic'ed'isms that do not conflict with historical BSD behaviour are available 3558344Sbosticto the user. 3658344Sbostic 3758344SbosticRefer to the man page ed(1) for information about using `ed'. 3858344Sbostic 3958344Sbostic-Rodney 40