Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aspell_dict_info_list_size always returns zero #155

Open
aspell-helper opened this issue Sep 9, 2004 · 6 comments · May be fixed by #645
Open

aspell_dict_info_list_size always returns zero #155

aspell-helper opened this issue Sep 9, 2004 · 6 comments · May be fixed by #645

Comments

@aspell-helper
Copy link
Collaborator

Nathan Fredrickson <noif@sf> created a bug report on 2004-09-09 01:56:57 UTC
(Orig. from https://sourceforge.net/p/aspell/bugs/98)

aspell_dict_info_list_size always returns zero
reguardless of how many dictionaries are actually
described in the list.

Test progam attached.
gcc -o test -laspell test.c

@aspell-helper
Copy link
Collaborator Author

Nathan Fredrickson <noif@sf> commented on 2004-09-09 01:56:58 UTC

test.c

@aspell-helper
Copy link
Collaborator Author

Kevin Atkinson <kevina@sf> updated the issue on 2004-09-10 11:56:55 UTC

  • labels: --> other
  • priority: 5 --> 2
  • assigned_to: nobody --> kevina
  • status: open --> open-postponed

@aspell-helper
Copy link
Collaborator Author

Kevin Atkinson <kevina@sf> commented on 2004-09-10 11:56:55 UTC

Logged In: YES
user_id=6591

Yeah I know. Its unimplemented.

@rrthomas
Copy link

Enchant maintainer here: I just looked at this issue because it tripped me up some years ago when I was working on the Enchant aspell back-end. As far as I can see, this API is still not marked as unimplemented. Could it be removed from the header file and/or marked as unimplemented, please? (Or even better, just implement it?)

Thanks for working on aspell all these years, @kevina !

@kevina
Copy link
Member

kevina commented Mar 23, 2024

I can mark it as unimplemented. I don't want to remove the function as that will break ABI comparability, and removing them from the header file will be difficult as the header file is automatically generated.

@rrthomas
Copy link

Removing a function that always returns zero seems to be a fairly small break, but I understand! Marking as unimplemented would have saved me the trouble I've had, so that would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants