From: George Lebl Date: Thu, 8 Jun 2000 08:48:00 +0000 (-0800) Subject: Release 1.0.1 X-Git-Tag: v1.0.1 X-Git-Url: https://git.draconx.ca/gitweb/gob-dx.git/commitdiff_plain/072bb12e618b26cce359784aa56f9a2b70e1ce52 Release 1.0.1 --- diff --git a/ChangeLog b/ChangeLog index 321e0fe..4b931f1 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,6 +1,23 @@ +Wed Jun 07 15:03:18 2000 George Lebl + + * Release 1.0.1 + +Wed Jun 07 14:41:24 2000 George Lebl + + * configure.in, doc/gob.1.in: updates + +Mon Jun 05 12:10:46 2000 George Lebl + + * doc/gob.1.in: run through ispell, and fix option stuff to produce + nicer html output with groff + +Thu Jun 01 18:12:13 2000 George Lebl + + * src/main.c: Make the private header switches work again. + Wed May 31 01:50:25 2000 George Lebl - * Relased 1.0.0 + * Release 1.0.0 Wed May 31 01:47:23 2000 George Lebl diff --git a/NEWS b/NEWS index a203af0..77cf571 100644 --- a/NEWS +++ b/NEWS @@ -1,3 +1,7 @@ +1.0.1 + * documentation fixes + * fix the behaviour of the private header switches + 1.0.0 * accept an identifier such as a constant in array dimensions * updated manpage with build instructions diff --git a/configure b/configure index 753ec48..3dc86a2 100755 --- a/configure +++ b/configure @@ -703,7 +703,7 @@ fi PACKAGE=gob -VERSION=1.0.0 +VERSION=1.0.1 if test "`cd $srcdir && pwd`" != "`pwd`" && test -f $srcdir/config.status; then { echo "configure: error: source directory already configured; run "make distclean" there first" 1>&2; exit 1; } diff --git a/configure.in b/configure.in index ef35700..9c8435c 100644 --- a/configure.in +++ b/configure.in @@ -2,7 +2,7 @@ dnl Process this file with autoconf to produce a configure script. AC_PREREQ(2.2) AC_INIT(src/treefuncs.h) AM_CONFIG_HEADER(config.h) -AM_INIT_AUTOMAKE(gob,1.0.0) +AM_INIT_AUTOMAKE(gob,1.0.1) if test -f ../NOINST_GOB ; then DOINSTGOB= diff --git a/doc/gob.1.in b/doc/gob.1.in index aa9b45d..9e1ce35 100644 --- a/doc/gob.1.in +++ b/doc/gob.1.in @@ -22,19 +22,13 @@ is in spirit similar to things like lex or yacc. .SH OPTIONS .PP .TP -.B -? -.TP -.B -h -.TP -.B --help +.B -? -h --help Display a simple help screen. .TP .B --version Display version information (note, --version was not added until 0.92.0) .TP -.B -w -.TP -.B --exit-on-warn +.B -w --exit-on-warn Exit with an error code even when you encounter a warning. .TP .B --no-exit-on-warn @@ -70,14 +64,12 @@ define the private data structure at the point in the .c source where the class definition begins. This option implicitly negates --always-private-header .TP -.B -n -.TP -.B --no-write +.B -n --no-write Do not write any output files, just check syntax of the input file. .TP .B --no-lines Do not print out the '#line' statements into the output. Useful for debugging -the autogenerated generated code. +the auto-generated generated code. .TP .B --no-self-alias Do not create the Self and SelfClass type aliases and the SELF, IS_SELF @@ -341,7 +333,7 @@ take up more space in the file and it may become more cluttered. .PP The data is zeroed out after being destroyed. This is to make debugging easier in case your code might try to access an already destroyed object. In case -you have overriden the destroy method, your code will be run first and +you have overridden the destroy method, your code will be run first and only then will the destructors be called. You should not however make any assumptions about the order at which the destructors are called. If you have interdependencies between destructors for different data members, you will @@ -434,7 +426,7 @@ is just like set { self->foo = ARG; }; .fi -Similiarly, +Similarly, .nf private char * foo; @@ -637,7 +629,9 @@ signal just like a public method. Example: ... } +.fi or +.nf signal last NONE(NONE) void foo(self); @@ -724,13 +718,13 @@ function. For example: } .fi Thus you see that the "_foo" method still generates the method "my_object_foo" -just as "foo" would generate. You can turn off this behaviour if you depend -on the old (pre 0.93.5) behaviour with the --no-kill-underscores option. This +just as "foo" would generate. You can turn off this behavior if you depend +on the old (pre 0.93.5) behavior with the --no-kill-underscores option. This also means that if both "_foo" and "foo" are defined, it is treated as a conflict. .PP This does not apply to override methods. Override methods are special beasts -and this is not neccessary and would make the code behave in weird ways. +and this is not necessary and would make the code behave in weird ways. .PP Making new objects: .PP @@ -752,7 +746,7 @@ Self alias casts: .PP There are some standard casts defined for you. Instead of using the full macros inside the .c file, you can use SELF, IS_SELF and SELF_CLASS. Using -these makes it easier to for example change classnames around. +these makes it easier to for example change class names around. .PP Self alias types: .PP @@ -809,7 +803,7 @@ compile with a C++ compiler. .SH IDENTIFIER CONFLICTS .PP -Gob will need to define some local varibles and functions in the generated +Gob will need to define some local variables and functions in the generated files, so you need to take some precaution not to conflict with these. The general rule of thumb is that all of these start with three underscores. There is one, "parent_class" which doesn't because it's intended for use in your @@ -824,7 +818,7 @@ PARENT_HANDLER macro. In fact avoiding all names with three underscores is the best policy when working with gob. .PP Also note that starting with version 0.93.5, method names that start with a -an underscore are eqivalent to the names without the initial underscore. This +an underscore are equivalent to the names without the initial underscore. This is done to avoid conflicts with the aliases. Thus you can define the method as "_name", if "name" happens to be some standard library function. This is the same as defining it as "name" except that the local alias will be "_name" @@ -852,7 +846,7 @@ indented any number of tabs or spaces and you can use the short method name without the type prefix. Gob will automatically try to extract these and translate to full names and put them in the output source file. An example would be: -.fi +.nf class Gtk:Button:Example from Gtk:Button { /** @@ -872,7 +866,7 @@ would be: .fi If the function you are documenting is a signal or a virtual then it will -be documentating the wrapper that starts that virtual function or emits +be documenting the wrapper that starts that virtual function or emits that signal. .SH DEALING WITH CIRCULAR HEADERS @@ -939,7 +933,7 @@ program. .SH BUGS .PP -Also the lexer does not actually parse the C code, so I'm sure that some corner +The lexer does not actually parse the C code, so I'm sure that some corner cases or maybe even some not so corner cases of C syntax might confuse gob completely. If you find any, send me the source that makes it go gaga and I'll try to make the lexer try to handle it properly, but no promises. @@ -978,6 +972,25 @@ Basically, if you use gob, just don't use the C preprocessor too extensively. Comments will not get through to the generated files unless inside C code. This makes using something like gtk-doc harder. However I'm planning to fix this somehow. +.PP +The short name aliases are actually implemented as pointers to functions. Thus +if you want to get the pointer of a function using the short name alias you +can't use the '&'. Thus: +.nf + + void (*foo)(Self *); + + /* this will NOT work */ + foo = &short_name; + + /* this will work */ + foo = short_name; + + /* Both of these will work */ + foo = &my_class_long_name; + foo = my_class_long_name; + +.fi .SH AUTHOR .PP diff --git a/gob.spec b/gob.spec index 94e0fd3..ac4d7ab 100644 --- a/gob.spec +++ b/gob.spec @@ -1,4 +1,4 @@ -%define ver 1.0.0 +%define ver 1.0.1 %define rel 1 %define prefix /usr diff --git a/src/main.c b/src/main.c index 6ab2cb9..31cd849 100644 --- a/src/main.c +++ b/src/main.c @@ -1774,7 +1774,7 @@ open_files(void) if((privates > 0 || protecteds > 0 || private_header == PRIVATE_HEADER_ALWAYS) && - !private_header != PRIVATE_HEADER_NEVER) + private_header != PRIVATE_HEADER_NEVER) outfileph = g_strconcat(filebase, "-private.h", NULL); else outfileph = NULL; @@ -2454,11 +2454,11 @@ parse_options(int argc, char *argv[]) } else if(strcmp(argv[i], "--no-touch-headers")==0) { no_touch_headers = TRUE; } else if(strcmp(argv[i], "--ondemand-private-header")==0) { - private_header == PRIVATE_HEADER_ONDEMAND; + private_header = PRIVATE_HEADER_ONDEMAND; } else if(strcmp(argv[i], "--always-private-header")==0) { - private_header == PRIVATE_HEADER_ALWAYS; + private_header = PRIVATE_HEADER_ALWAYS; } else if(strcmp(argv[i], "--no-private-header")==0) { - private_header == PRIVATE_HEADER_NEVER; + private_header = PRIVATE_HEADER_NEVER; } else if(strcmp(argv[i], "--no-gnu")==0) { no_gnu = TRUE; } else if(strcmp(argv[i], "--no-extern-c")==0) {