[pyicu-dev] towards release 1.0
friedel at translate.org.za
Wed Mar 31 14:49:01 PDT 2010
Op Wo, 2010-03-31 om 10:29 -0700 skryf Andi Vajda:
> On Wed, 31 Mar 2010, F Wolff wrote:
> > I get lots of warnings about "deprecated conversion from string constant
> > to ?char*?" (I can give the complete output if you want), but it
> > eventually fails with
> If you're using a gcc 4.x compiler, add -Wno-write-strings to the CFLAGS for
> your platform in setup.py to silence these warnings.
> > search.cpp:594: error: ?USEARCH_ELEMENT_COMPARISON? was not declared in this scope
> > search.cpp:601: error: ?USEARCH_STANDARD_ELEMENT_COMPARISON? was not declared in this scope
> > search.cpp:602: error: ?USEARCH_PATTERN_BASE_WEIGHT_IS_WILDCARD? was not declared in this scope
> > search.cpp:603: error: ?USEARCH_ANY_BASE_WEIGHT_IS_WILDCARD? was not declared in this scope
> > error: command 'gcc' failed with exit status 1
> > I don't see USEARCH_ELEMENT_COMPARISON (or any of the other three)
> > anywhere in my installed header files for icu.
> Yes, these are in fact 4.4 features. I had mistakenly conditionalized them
> on 4.0. Now fixed in trunk rev 131.
> > Does that help? I'm not sure what else you would need, so feel free to
> > ask for any extra information.
> Yes, this is what I need.
Warnings and errors gone now. Now looking through the Python API for
the first time. Thanks for the help!
The first thing that strikes me, is that I'll need to get familiar with
the C API before I can use this. Would it be possible to get some of the
C documentation into the docstrings? It would make it more useful in
itself, and will be more accessible to programmers who don't know C that
Talking about PEPs - just checking: do we want to keep the camel case
capitalisation to stay close to the C library?
I might be able to help with some of this if I have a good example to go
by. Is this something that everybody wants?
Recently on my blog:
More information about the pyicu-dev