On Thu, 25 Jul 2013, Mark Hofmann wrote to Gene Buckle:

GB> It really shouldn't take much to add FOSSIL support to that code Mark.

 MH> Fossil support was added to WWIV 4.30 and greater. 

 MH> I have the source to 4.30 and it looked to me like the fossil
 MH> support was a total re-write of the communications in all the
 MH> modules.  It has hooks into everything, so it wasn't something that
 MH> I could add in without spending a good deal of time on it.

agreed... the deal is that you either talk to the FOSSIL or you talk to the
serial port handling everything the FOSSIL does on your own... a system
that can use both is going to be a bit larger and more convoluted than one
that doesn't... but the key switch is if the "use FOSSIL" setting
is 'true' or 'false'... everything else should be the same... all the calls
to all the routines and everything...

for example, in pascal

  writeln ("this is one line written to the screen");

then if one wanted to send it out the modem line as well they might have

  xmitln ("this is one line written to the modem");

both of these may be encapsulated in one routine that is used everywhere to
send text to the screen and modem at the same time...

  sendln ("this is one line sent to the screen and the modem");

and sendln might look like

  procedure sendline (theline;string);

  begin
    writeln(theline);
    xmitln(theline);
  end;

then all the deep comms magic would take place in xmitln and it would
determine if it was to send the output thru the own serial comms stuff or
if it was to send it over to the FOSSIL sending code...

i remember, back in the day, fighting serial comms a lot... then i found
the FOSSIL stuff, ripped out everything i had been fighting with and just
talked to the FOSSIL from then on... all the problems were solved in an
instant... the projects then only needed to load x00 or bnu and off we
went...

)\/(ark

--- FMail/Win32 1.60