Timeline for Parsing Valve Map Files (VMF) into a tree like structure
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 9, 2014 at 17:42 | vote | accept | BenVlodgi | ||
| Mar 26, 2014 at 19:17 | history | edited | BenVlodgi |
added tag
|
|
| Mar 21, 2014 at 1:24 | comment | added | svick | That's the problem when you don't have a formal spec: is that actually invalid syntax, or are the newlines that I think you are expecting there optional? | |
| Mar 21, 2014 at 1:20 | answer | added | svick | timeline score: 8 | |
| Mar 21, 2014 at 1:02 | answer | added | svick | timeline score: 5 | |
| Mar 21, 2014 at 0:53 | comment | added | BenVlodgi | @svick There is a wiki page on this, however some examples have invalid syntax to save space developer.valvesoftware.com/wiki/Valve_Map_Format like anywhere you have a block name followed by empty {} | |
| Mar 21, 2014 at 0:13 | comment | added | BenVlodgi | not as far as I've seen, and as long as it works with hammer and the compiler, it doesn't matter... it doesn't really throw curveballs | |
| Mar 20, 2014 at 23:19 | comment | added | svick | Isn't there a format specification for the language? Just to make sure that you covered every possible edge case correctly. | |
| Mar 20, 2014 at 20:19 | history | edited | BenVlodgi | CC BY-SA 3.0 |
added 31 characters in body
|
| Mar 20, 2014 at 19:12 | history | asked | BenVlodgi | CC BY-SA 3.0 |