Re: Rep:Re: Error Writing/Reading Encrypted Values

Cedar Cox wrote:
>
> > > > > Ok. I understand the dilemma. In that case, perhaps it would make sense
> > > > > for it to be a compile time option, with defaults as I mentioned. It
> > > > > seems most likely to be platform dependent, and probably set only once
> > > > > anyway. This way the windows driver at least wouldn't change at all
> > > > > ...back to the list. Comments anyone?
> > > >
> > > > Compile-time options are even less attractive -- perhaps some
> > > > auto-sensing code that looked at the first line and determined the
> > > > proper behavior.
> > >
> > > Hmm I don't understand what auto-sensing means.
> > > At any rate I would change the behavior in the next
> > > version.
> >
> > For auto-sensing, I was thinking of looking at the end of the first line
> > and seeing if it is \n or \r\n and using that to handle the rest of the
> > lines.
>
> The point of this is to handle arbitrary binary data (and give people an
> option of CRLF translation) right? What if the "wrong" data appears?
> How does one auto-sense binary data? (Perhaps I'm missing something..)

It was just a guess. I thought it was dealing with end-of-line issues.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026