8 Srp
2013
8 Srp
'13
11:06
That has a simple solution - keep unquoted strings where you use strings as
identifiers/tokens and use quoted strings if it's a value.
Ondřej Surý
On 8. 8. 2013, at 9:53, Peter Andreev
<andreev.peter(a)gmail.com> wrote:
2013/8/7 Ondřej Caletka <ondrej.caletka(a)gmail.com>
Hi Marek,
Dne 6.8.2013 17:17, Marek Vavrusa napsal(a):
I am thinking of disallowing unquoted strings in
the next release, hope there's no big fan of this. Is there?
Do you mean that config file should look like this?
---cut---
remotes {
"slave0" {
address 203.0.113.1@53;
}
"slave1" {
address 198.51.100.1@53;
}
}
zones {
"example.com" {
file "/etc/knot/example.com.zone";
xfr-out "slave0", "slave1";
notify-out "slave0", "slave1";
}
}
---cut--- In that case, I would vote for keeping unquoted
strings allowed.
However, if quoting would be required only in possibly ambiguos fields,
I would have no problem with that.
It will be ambiguously in itself.
From my point of view, strictly following to defined rules is better. Of course, if rules
are defined at all.
Cheers,
Ondřej Caletka
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
--
Is there any problem Exterminatus cannot solve? I have not found one yet.
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users