On Tue, 5 Aug 2003, Jinx wrote:

> > what's your conception of documentation?
> > "Why not?" is not a conception.
> >
> > Wouter van Ooijen's conception is quite clear:
> > > If it were a parameter it should indeed be in the datasheet.
> > > But it is one (anf just one) way of using the pin, and I don't
> > > want all the ways of using a pin cluttering the datasheet.
> >
> > It seems you have been Microchiping too long, Jinx.  :-)
>
> Or not long enough, some might say
>
> > A set of documentation _MUST_ be orthogonal. Like a set of
> > commands, like a chip architecture.
> > MChip is pretty notorious for violating these basic rules.
> >
> > Mike.
>
> At the risk of dragging this out and becoming the RA4 poster
> boy (and it's too nice a day to be a-feudin' anyway)
>
> The manual covers the usage of other special pins, such as
> MCLR, OSC, A/D etc. Surely a brief sentence along the lines
> of "RA4 may require a pullup if used as an I/O pin" is valid
> information for a manual ?

  Definitely not. It's just an information which must be provided
at any "basic of electronics" course. A clever user must know how to
use an open colector, open drain or open source device. If does not,
than must learn first.

Vasile

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads