-Very simple preprocessor for making GTK+ objects with inline C code so that
-generatedfiles are not editted. Syntax is inspired by java and yacc or lex.
+GObject Builder (GOB-2)
+(George's Obfuscated Bits)
+
+Very simple preprocessor for making GObject objects with inline C code so that
+generated files are not editted. Syntax is inspired by java and yacc or lex.
The implementation is intentionaly kept simple, and no C code parsing is done.
Reasons:
- C is a perfect (well mostly) language, no need for another language
The implementation is intentionaly kept simple, and no C code parsing is done.
Reasons:
- C is a perfect (well mostly) language, no need for another language
- Need for a generator that doesn't require changes to generated code
- I like how Java writes method code directly into the class
definition.
- Need for a generator that doesn't require changes to generated code
- I like how Java writes method code directly into the class
definition.
What's generated:
two (.c and .h) files named by the object name with words
separated by a hyphen (not neccessairly the .gob file prefix)
How to write .gob files?
What's generated:
two (.c and .h) files named by the object name with words
separated by a hyphen (not neccessairly the .gob file prefix)
How to write .gob files?
2) if you can't find what you need, read src/test.gob for an
example of GOB code
3) If you still can't find what you need, read src/lexer.l
and src/parse.y (in other words: RTFS)
2) if you can't find what you need, read src/test.gob for an
example of GOB code
3) If you still can't find what you need, read src/lexer.l
and src/parse.y (in other words: RTFS)
project directory. Use the AC_CONFIG_SUBDIRS to include that
directory in your configure run. And finally add a file called
NOINST_GOB into your toplevel project directory (this can be done
project directory. Use the AC_CONFIG_SUBDIRS to include that
directory in your configure run. And finally add a file called
NOINST_GOB into your toplevel project directory (this can be done
- inside your configure script in fact) so that gob doesn't install
- itself. Then just use the made gob binary as you would other
+ inside your configure script in fact) so that gob2 doesn't install
+ itself. Then just use the made gob2 binary as you would other