Read Me
2026.11.08 Miroslaw Dobrzanski-Neumann (mirek-dn@freenet.de)
It's still Work In Progress
- whole reository builds successfully
- use ./setup.sh to setup and run first build
afterwards you can use make
it performs a build out-of-source
suppose you cloned at ~/DEV/freedce-dev
then it creates ~/DEV/freedce-build and ~/DEV/freedce-inst
and runs build process in ~/DEV/freedce-build
after dcethreads are built it is installed in ~/DEV/freedce-inst
and referenced there
there is a bug in "dceidl" that lets it crash at times, reason unknown
2026-10-28 Miroslaw Dobrzanski-Neumann (mirek-dn@freenet.de)
It's Work In Progress
WHAT WORKS:
1. DCE threads are working yo you can use them
1.1 New / missing freatures implemented
- EXCEPTION handling fully implemented so you can use all of them
TRY, CATCH, CATCH_ALL, FINALLY, ENDTRY
A nice solution for ordering the blocks will be welcome
for instance no FINALLY before CATCH and the like
what is allowed is C23 (not C++) with its preprocessor
please note:
DCE threads are based on pthreads draft 4
current version is draft 10 aka NPTL, at places there are differences in semantics
dcethreads are here implemented ontop of the current pthreads standard (NPTL)
so it should be safe to use parts in current software
Exceptions are safe anyway
WHAT DOESNT WORK: FREEDCE
It is WIP (Work In Progress)
1. idl compilation errors
2. crashes in at some places
WISH LIST:
- as mentionend above, enforcement of block ordering in TRY/ENDTRY
- tests,
please note here are only the autotools tests used, no other framework
take a look at the existing ones