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

Functionality that differs across platforms needs to be isolated for portability. #4

Open
GoogleCodeExporter opened this issue Mar 12, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

In order to make muSE more portable across platforms, the portion of the
code that changes across platforms needs to be isolated so that ports can
be added systematically.

Original issue reported on code.google.com by srikuma...@gmail.com on 25 Sep 2006 at 1:28

@GoogleCodeExporter
Copy link
Author

Aspects include -

1. Memory allocation.
     - malloc, free, calloc, realloc, alloca

2. Heap scheme - need to change the monolithic heap to a segmented heap for 
memory
constrained platforms.

3. UTF8 <-> unicode conversions

4. Networking

5. File I/O

6. Diagnostics

7. call/cc

8. File system access

Original comment by srikuma...@gmail.com on 25 Sep 2006 at 1:31

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

No branches or pull requests

1 participant