se-Skarstad « dvb-t - dtv-scan-tables.git - Digital TV scan tables

about summary refs log tree commit diff stats

path: root/dvb-t/se-Skarstad

blob: edc1aac09ce55891ee5aae3b7cd0fe6c319bc38e (plain)

1
2
3

# Sweden - Skärstad
# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
T 610000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE

.s1 { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Single */ .highlight .ss { color: #aa6600; background-color: #fff0f0 } /* Literal.String.Symbol */ .highlight .bp { color: #003388 } /* Name.Builtin.Pseudo */ .highlight .fm { color: #0066bb; font-weight: bold } /* Name.Function.Magic */ .highlight .vc { color: #336699 } /* Name.Variable.Class */ .highlight .vg { color: #dd7700 } /* Name.Variable.Global */ .highlight .vi { color: #3333bb } /* Name.Variable.Instance */ .highlight .vm { color: #336699 } /* Name.Variable.Magic */ .highlight .il { color: #0000DD; font-weight: bold } /* Literal.Number.Integer.Long */

TO-DOs:

These are features that have been requested, and have been considered,
but are not yet implemented, because I'm undecided about how or whether they
should be implemented, and/or because they are difficult and/or time-consuming
to implement.

Also, some of these features tend to push libconfig toward becoming a
general-purpose structured-data storage mechanism, which is really not the
intended purpose of this library. I think something like sqlite is better
suited for that sort of thing.


* Add an option for safe type conversions; that is, report an error
  rather than silently truncating out-of-range values to 0 (namely int64 ->
  int).


* Add support for copying settings from one configuration to another. Need a
  recursive function to copy a setting and call itself on all child settings.


* Add a += operator, so that additional elements can be appended to a list or
  array. The issue with this is defining a consistent syntax. For example:

  x = ( 1, 2, 3 );
  x += ( 4, 5 );

  Should this result in ( 1, 2, 3, 4, 5 ), or ( 1, 2, 3, ( 4, 5 ))? I believe
  it should be the latter. However, only the former makes sense for arrays.


* Add the ability to insert/delete elements at any position in a list or
  array. A simple implementation would be expensive (shift all the elements
  by one for every insert/delete), and a more efficient implementation would
  add a lot of complexity to the library.


* Add limited support for preserving comments?


* Add support for unicode strings? A bit problematic, since flex doesn't
  support unicode input, AFAICT. But maybe supply convenience functions to
  convert between parsed UTF-8 strings and std::wstring.