View Issue Details

IDProjectCategoryView StatusLast Update
0002500unrealircdpublic2005-05-26 16:25
ReporterMeDevil Assigned To 
PrioritynormalSeveritytrivialReproducibilityalways
Status closedResolutionopen 
Product Version3.2.4 
Summary0002500: configuration parsing...
Descriptioni've noticed that blocks with no space between name and { gives a configuration error. example:

admin { // No error
  "...";
};

admin{ // Error
  "...";
};

I know that is fu**** ugly but i think that should
not be considered as an error.

What is your opinion about this?
3rd party modules

Activities

MeDevil

2005-04-25 10:14

reporter   ~0009807

a little error:
Product Version is <= 3.2.3

vonitsanet

2005-04-25 13:33

reporter   ~0009808

Of COURSE it should be an error here.. Nothing more.

MeDevil

2005-04-25 15:16

reporter   ~0009809

Sorry, i don't understand.
Why we should considered this an error?

I think that "admin {" and "admin{" (or any other block) are the same thing...
i'm wrong?

Stealth

2005-04-25 17:34

reporter   ~0009810

I don't see a reason Unreal should accept this. If you have "block{" all over your config, it is a bad config anyway. The block-style config is made to look and be clean, and "block{" is far from clean.

MeDevil

2005-04-26 04:00

reporter   ~0009812

I don't see a reason Unreal shouldn't accept this...
I've noticed (by exploring the source files) that you can use
something like: "my{module}-{conf} {" and Unreal will not blame you.
so my question is: is this better than allowing "admin{" ?
imho configuration tokens should not be allowed in block names
(and this will make "me{" perfectly legal)

i'm a c/c++ developer, and sometimes i have to write code in a really ugly way
(i mean how does it appear, not how does it work :P), just because i want to
fit a line in 80 columns, and the compiler will not blame me just because i've
written "if(xx){function();}else{function2();}". (but it will do if i try to use a function such as "fanny{funct}ion(xxx){" ).

in conclusion, i think that "me{" is less ugly than "my{module}-{conf} {".

syzop

2005-04-26 21:54

administrator   ~0009823

It's not a strong argument or anything, but if one would accept this then things like: ban nick { mask somenick{17}; reason "go away"; }; would be broken.

I think we should keep it as-is... There's not much "added value" here anyway.

Issue History

Date Modified Username Field Change
2005-04-25 09:02 MeDevil New Issue
2005-04-25 10:14 MeDevil Note Added: 0009807
2005-04-25 13:33 vonitsanet Note Added: 0009808
2005-04-25 15:16 MeDevil Note Added: 0009809
2005-04-25 17:34 Stealth Note Added: 0009810
2005-04-26 04:00 MeDevil Note Added: 0009812
2005-04-26 21:54 syzop Note Added: 0009823
2005-05-26 16:25 syzop Status new => closed