> > I know. Once I thought about sed/awk magic to generate two different > > modules from one template. > > What about symlinks, like: > > bsd18module.c -> bsd30module.c > bsd30module.c > > and using a few #ifdefs in the C sources? Instead of symlinks, how about one .h file containing most of the code and two or three .c files that set a few #defines and then #include the .h file? Similar to what we do for Python/threads.c --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4