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

Switch to LGPL instead #1

Open
XVilka opened this issue Mar 16, 2020 · 2 comments
Open

Switch to LGPL instead #1

XVilka opened this issue Mar 16, 2020 · 2 comments

Comments

@XVilka
Copy link

XVilka commented Mar 16, 2020

To be able to use this as library.

We are considering this for https://github.com/radareorg/radare2/issues/6093

@catb0t
Copy link
Owner

catb0t commented Mar 18, 2020

In its current state, this project is an unfinished, highly experimental toy.

It lacks a lot of basic functionality, and the functionality it does have is currently naively implemented using a lot of copies/frees (instead of in-place data changes, because of strong const correctness), and the most simple algorithms possible, to teach myself the principles.

On top of all that, its core premise is probably wrong, and whatever strategies are used by GMP, Boost, etc to fit large numbers in small amounts of memory should probably be used instead of simple arrays, but currently aren't used.

However, if you are still interested, it can be made production-efficient, especially with contributions.

@catb0t
Copy link
Owner

catb0t commented Mar 18, 2020

Your application is specifically for the representation of wider hardware types, so a purpose-built library which can use wider hardware types when available, but falls back to a platform-independent representation otherwise, would probably be best. That might be fun to work on.

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

No branches or pull requests

2 participants