Re: Q: Extending nntp (for nndb)

[Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de>]

>>>>> On 27 Mar 1996 04:49:37 +0000, Lars Magne Ingebrigtsen
>>>>> <larsi@ifi.uio.no> said:

  Lars> By "data", the manual means "data in the nntpd buffer".  I
  Lars> forgot to mention the function return value.

I see.  By  reading a bit more, I found that there is in fact one
function where the return value is mentioned: a list of article
numbers.  Can I assume that this is the same for other functions?

  Lars> The `*-open-server' function sets all variables in the
  Lars> backend.  So all the other functions can assume that they are
  Lars> working on variables local to the current virtual server.

So if I were to add to the nntp.el file a new function, said function
could just use the variable nntp-address to get the name of the nntp
server?

  Kai> Maybe this was a completely stupid approach of doing it?
  Kai> Should I've copied nntp.el then change every occurrence of
  Kai> "nntp" to "nndb", then change the defaults at will?

  Lars> Yes, probably.  nndb and nntp are sufficiently different that
  Lars> there probably should be a new nndb.el file.

Really?  Please note that nndb offers a superset of the nntp protocol.
Therefore, the nntp subset would have to be maintained twice if the
two were completely independent nndb.el and nntp.el files.  Well, I
don't like this idea, but you're the guru, so I'll comply.

Why is ELisp not object-oriented?

        kai
--
There ain't no cure for the summer time blues.