View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002276 | unreal | ircd | public | 2005-01-12 01:14 | 2007-04-27 05:22 |
| Reporter | fez | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | wont fix | ||
| Product Version | 3.2.2 | ||||
| Summary | 0002276: config directive parsing | ||||
| Description | Well, here's another thought I had, all over the documentation the notation block::subblock::directive is used to describe supported config options, however you actually have to type in block { subblock { directive; }; }; to use it, which can confuse a lot of people (esp. those who aren't familliar with the origin of this syntax, taken from c++ class definitions. So, I was thinking, perhaps the config parser could actually allow the literal "::" notation so you could easily add a one-liner to your config like set::options::special-option "whatever"; What do you think? -- fez / Eric | ||||
| 3rd party modules | |||||
|
|
Sounds good, I have talked to someone about this in the past on #Unreal-Support, but that didnt go too well... Maybe a real feature request might be enough :) |
|
|
I don't know about this. Yeah, for set it might be useful. But what about when the documentation mentions allow::ip? That *must* be contained within a block, so how do we interpret that? If allow::ip "*@*"; is found, there is no way to understand that. So this might lead to more confusion... |
