File: TODO

package info (click to toggle)
scummvm 2.9.1%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 450,580 kB
  • sloc: cpp: 4,299,825; asm: 28,322; python: 12,901; sh: 11,302; java: 9,289; xml: 7,895; perl: 2,639; ansic: 2,465; yacc: 1,670; javascript: 1,020; makefile: 933; lex: 578; awk: 275; objc: 82; sed: 11; php: 1
file content (33 lines) | stat: -rw-r--r-- 948 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
This is an -*- Outline -*- of ideas for future versions of CxxTest.
It is not meant to be "human readable".

* CxxTest To Do list

** Mock framework

Write some mocks

*** Distribution
Separate packages (w/ binaries)?  How would that be used?
For Windows: .lib for "Real" and "Mock" parts.
For Linux: Maybe. Different compilers etc.
So probably only source release with Makefiles and .ds[pw]?  Or just Win32 binary.

**** Installation?
extract cxxtest-x.y.z.tar.gz
(extract cxxtest-mock-x.y.z.tar.gz) ?
make -C cxxtest/Real
make -C cxxtest/Mock

or maybe make -C cxxtest -f Makefile.mock
but then Makefile.mock.bcc32, Makefile.mock.msvc, Makefile.mock.gcc, and heaven knows what else.

Could put the Makefile.mock.* in cxxtest/Real and cxxtest/Mock or in cxxtest/T

Maybe this should be a different package altogether?
Seems logical, since they evolve separately.  But then you'd want to download both.

** Thoughts
-fomit-frame-pointer

** TS_HEX