Open GoogleCodeExporter opened 9 years ago
Some details on key-value format:
* This is the format we use for config files
* Both /* C comments */ and // C++ comments are allowed
* Composed of tokens that are one of:
- an_Identifier_Without_Quotes
- "A double quoted string" 'or a singly quoted string'
- -1.23456
* Identifiers cannot start with a dash or number but may contain one
* Statements come in pairs starting with one key token and one or more value
tokens
* String and numerical tokens are allowed to concatenate and spread over
multiple lines:
my_string "the value of this var is"
"wrapped over multiple lines"
my_number 3.14
159265
Original comment by risu...@gmail.com
on 15 Apr 2008 at 1:28
I can do this starting Saturday if no one else can. But until then I have 2
Exams so
I have no time.
Original comment by Kas...@gmail.com
on 15 Apr 2008 at 7:05
Kasuko: it's yours. Please remember to go over the wiki for coding style and
issue
tracker rules. Original issue filed:
http://code.google.com/p/plutocracy/issues/detail?id=28
GenLang is now committed, but that issue has my original versions attached. Ask
me if
you have any questions about how it works.
Original comment by gar...@gmail.com
on 16 Apr 2008 at 4:45
Make sure that the parser can handle this amount of stress:
http://amanieu.homelinux.com/test_input.txt
http://amanieu.homelinux.com/test_output.txt
</evil>
Original comment by gar...@gmail.com
on 16 Apr 2008 at 10:20
If possible, also try to add a line number and source file above the //
English, like
this:
// plutocracy.c:200
// English: blah blah blah
Original comment by amanieu
on 17 Apr 2008 at 9:08
[deleted comment]
[deleted comment]
The stress test, although it works, it's in fact a special case as the string
contains a /* <stuff> *///<stuff> so it doesn't break but if it wasn't the last
line
or there wasn't a C++ style comment after the C style comments end it will cause
problems. I will sanitize the string by changing "*/" to "* /" so the C style
comment
will only end when the file tells it to end.
Original comment by Kas...@gmail.com
on 24 Apr 2008 at 3:00
genlang.py now preserves changes, but can't quite get Deprecation to work.
Original comment by Kas...@gmail.com
on 24 Apr 2008 at 6:28
Changing the status of this to 'Stalled' since we can't get in touch with
Kasuko. If
anyone is up for it, please grab this issue.
Original comment by risu...@gmail.com
on 27 May 2008 at 3:14
This should be an easy issue since it is well-separated from the rest of the
program.
Original comment by risu...@gmail.com
on 7 Jun 2008 at 5:42
Kasuko's AWOL. Any takers?
Original comment by risu...@gmail.com
on 20 Jun 2008 at 9:29
Enhancement -> Feature
Original comment by risu...@gmail.com
on 17 Jul 2008 at 11:22
Enhancement -> Feature (again)
Original comment by risu...@gmail.com
on 17 Jul 2008 at 11:25
Contribute tag
Original comment by risu...@gmail.com
on 17 Jul 2008 at 11:30
Original comment by risu...@gmail.com
on 18 Jul 2008 at 2:11
The latest game requirements include matching strings in Python code (there
aren't
any yet) and messages transmitted via N_send. These require just adding more
regular
expressions and probably adding .py files to the ones checked.
Original comment by gar...@gmail.com
on 1 Nov 2008 at 4:48
Original comment by gar...@gmail.com
on 1 Nov 2008 at 5:07
Original issue reported on code.google.com by
risu...@gmail.com
on 14 Apr 2008 at 8:21