[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Please try (Also, 0.2.0.x is now branched.)


Hi, all.  If you haven't already, it would be really helpful to the
development process if you could try Tor in the next few
days and let us know whether it works for you.  This is especially
important for people who have been happy with 0.1.1.x Tors up till
now: we really want to know whether there are any issues that will
stop anybody from upgrading to the 0.1.2.x series.

(There is a known bug where Tor does not work with old
versions of Windows (95, 98, and Me).  If you're running one of those,
you'll want to wait until  Sorry about that, and thanks
again to norvid for reporting the bug.)


This is just a regular reminder: if you build Tor from source, it
should compile without warnings.  Please send me mail if it doesn't.

(For extra excitement, if you're using GCC, you can run the configure
script with --enable-gcc-warnings and get GCC to add even more
warnings.  The list currently stands at:
    -Wall -W -Wfloat-equal -Wundef -Wpointer-arith Wstrict-prototypes
    -Wmissing-prototypes -Wwrite-strings -Wredundant-decls
    -Wchar-subscripts -Wcomment -Wformat=2 -Wwrite-strings
    -Waggregate-return -Wmissing-declarations -Wredundant-decls
    -Wnested-externs -Wbad-function-cast -Wswitch-enum -Werror
    -Winit-self -Wmissing-field-initializers
    -Wdeclaration-after-statement -Wold-style-definition

Again, if any of these warnings actually trigger anywhere in the code,
please let me know.  We try to write the cleanest C we possibly can,
and we hope it shows. ;)


If you have been tracking Tor development code via subversion, we just
branched the 0.1.2.x series off from the main branch.  Development of
0.1.2.x will continue on the branch:
and the new latest development series will continue to be at:

many thanks,
Nick Mathewson

Attachment: pgpIiV2TZSSgf.pgp
Description: PGP signature