Subject:
|
Re: Error in 71427.dat
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Sun, 10 Jan 1999 22:49:52 GMT
|
Viewed:
|
3288 times
|
| |
|
|
On Sun, 10 Jan 1999 21:46:25 GMT, "John Bauman" <jtb86@ptdprolog.net>
wrote:
> Terry K wrote in message <369847b6.1503620@lugnet.com>...
> > On Sun, 10 Jan 1999 03:20:31 GMT, "John VanZwieten"
> > <john_vanzwieten@msn.com> wrote:
> >
> > I get errors like this all the time in the new parts. I had to make
> > it a habit of visually scanning each part file submitted to me just
> > for that reason.
> > I am sure that it is not the authors fault. Long lines have a
> > tendency to get wrapped in various ways.
> > I remember I always had a real hard time with Tom Burger's parts -
> > somehow, his system and mine always seemed to conflict. Just about
> > every part he would send me would get mangled. And since his piece
> > code looked virtually the same as anyone else's, I just assumed that
> > something between he and I was screwing it up.
> Just run the file through l3p.It tells you where the errors are
Tom's parts were a while before l3p was released.
That does work, but it is not always any easier than just scanning the
file in a text editor.
L3p often will produce a ream of data on errors in the part. Most of
those errors I have no ability to fix. So scanning through that data
looking for the simple things I can correct takes longer than looking
through the file itself. (sigh)
Actually, ldlite can be set to log errors it encounters in a part. It
doesn't concern itself with the detail of errors that l3p does, so it
might be a better solution for my needs. I am going to try it and
see.
-- Terry K --
|
|
Message is in Reply To:
 | | Re: Error in 71427.dat
|
| Terry K wrote in message <369847b6.1503620@lu...et.com>... (...) Just run the file through l3p.It tells you where the errors are (...) (28 years ago, 10-Jan-99, to lugnet.cad)
|
14 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
