Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!cmcl2!husc6!uwvax!caip!clyde!burl!ulysses!cbosgd!mark
From: mark@cbosgd.UUCP (Mark Horton)
Newsgroups: net.news.adm
Subject: Re: Useful #L entries in uucp map (was "Re: a foolish consistency...")
Message-ID: <2501@cbosgd.UUCP>
Date: Mon, 1-Sep-86 23:56:11 EDT
Article-I.D.: cbosgd.2501
Posted: Mon Sep  1 23:56:11 1986
Date-Received: Tue, 2-Sep-86 07:04:55 EDT
References: <5048@decwrl.DEC.COM> <15454@ucbvax.BERKELEY.EDU> <432@epimass.UUCP> <339@maynard.UUCP> <940@cit-vax.Caltech.Edu>
Organization: AT&T Bell Laboratories, Columbus, Oh
Lines: 16
Keywords: uucp map graph(1G) awk source

Would one of you folks who has been writing a program to parse the map
data be so kind as to create a modified version of your program which
can be easily used to check the data for syntax errors?  It should
produce error messages that can be easily used to find the offending
line, e.g. mention the file and line number.  It should not produce
plotter output or require anything other than vanilla UNIX to compile.

The more it checks, the better, but if you just use your parsing code
for whatever data you use (lat/long, maybe the phone number, sure would
be nice to check the postal address too) we can ask our map coordinators
to run it when they update the database, and hopefully eliminate this
sort of syntax error.

If such a program already exists and I missed it, I apologize in advance.

	Mark