[hylafax-devel] Re: My RTN patch and many other changes/enhancements, third edition :-)

[Tim Rice <tim@trr.metro.net>]

On Fri, 14 Apr 2000, Aidan Van Dyk wrote:

> On 14 Apr, Dmitry Bely wrote:
> >> 
> >> Hmm, looking at your patch I'm thinking that things like
> >> ...
> >> static const NSFData KnownNSF[] =
> >> {
> >>     {"\x00\x00\x09", NULL,        false },
> >>     {"\x00\x00\x0E", "Panasonic", false, 3, 4, Panasonic0E },
> >>     {"\x00\x00\x11", "Canon",     false },
> >>     {"\x00\x00\x19", "Xerox",     true  },
> >> ...
> >> should be read from a config file at runtime so you don't have to
> >> recompile when you add to the list.
> > 
> > May be, but then we have to check their correctness, and explain in detail
> > to each and every newbie, how to edit this configuration data. Definitely
> > not now :-)
> 
> These entries should be fairly static...  I figure they should contain
                          ^^^^^^
> the devices that the "developpers" have identified.  Once the set is
> made, changes should be few and far between (hopefully).

I guess if "fairly static" means it doesn't change more than about once
a year it would be OK to compile in. But that seems to be contrary
to the design of HylaFAX where most anything in the software can 
be changed with config files.

> 
> A configuration file would be easy now while it is being gathered, but I
> think a compiled list is better for the release.
> 
> a.
> 
> 

-- 
Tim Rice		Multitalents	(707) 874-1130 (voice)
tim@trr.metro.net


____________________ HylaFAX(tm) Developers Mailing List ____________________
 To unsub: mail -s unsubscribe hylafax-devel-request@hylafax.org < /dev/null