The component synspellcheck is probably obsolete or is not compatible with new uniSynEdit...
Constantly gives out errors in an operating time Delphi7 IDE...
I see that in version 1.2.2 there is a C interface included in hunspell (hunspell.cxx and hunspell.h).
It's seems redundant with the Delphi interface, but it's missing a way to free suggestion results though.
In fact it should probably exists when used from C code too, because you don't know what memory allocator the caller is using.
This would allows to have only one interface maintained into hunspell.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are right, a single C interface is enough. I have attached a patch to extend the default C interface (src/hunspell/hunspell.h) with free_list() to solve the memory allocation problem under Delphi, C# etc. Next Hunspell release will contain it, if it works well. Thanks for your report and comment.
File Added: hunspell_free_list.patch
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=628902
Originator: NO
I see that in version 1.2.2 there is a C interface included in hunspell (hunspell.cxx and hunspell.h).
It's seems redundant with the Delphi interface, but it's missing a way to free suggestion results though.
In fact it should probably exists when used from C code too, because you don't know what memory allocator the caller is using.
This would allows to have only one interface maintained into hunspell.
patch - add free_list() to the default C interface
Logged In: YES
user_id=726595
Originator: NO
You are right, a single C interface is enough. I have attached a patch to extend the default C interface (src/hunspell/hunspell.h) with free_list() to solve the memory allocation problem under Delphi, C# etc. Next Hunspell release will contain it, if it works well. Thanks for your report and comment.
File Added: hunspell_free_list.patch
Logged In: YES
user_id=726595
Originator: NO
The newest Hunspell release contain a free_list() method for different memory allocator issue.
Doesn’t that solve this issue?