Subject | V4_THREADING |
---|---|
Author | Jim Starkey |
Post date | 2003-12-12T22:26:15Z |
The conditional V4_THREADING controls whether the code is thread safe.
While it can be set manually (I suppose), it is automatically defined by
the conditional SUPERSERVER.
I suggest that consideration be given to eliminating V4_THREADING in
toto making all builds containing code for maintain thread safety, not
just superserver. The reasons for this are:
1. Thread safety is critical in modern embedded usage.
2. The code base will be smaller and simpler
3. Future efforts to increase thread granuality will be made much
more difficult if non-thread safety is maintained as a build option.
4. If a demented individual wants to make a special non-thread safe
version, it is easier to conditionalize the implementation of the
synchronization primitives than a zillion calls to said primitives.
My most humble recommendation is that the V4_THREADING be yanked from
the FB 2 code tree.
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376
[Non-text portions of this message have been removed]
While it can be set manually (I suppose), it is automatically defined by
the conditional SUPERSERVER.
I suggest that consideration be given to eliminating V4_THREADING in
toto making all builds containing code for maintain thread safety, not
just superserver. The reasons for this are:
1. Thread safety is critical in modern embedded usage.
2. The code base will be smaller and simpler
3. Future efforts to increase thread granuality will be made much
more difficult if non-thread safety is maintained as a build option.
4. If a demented individual wants to make a special non-thread safe
version, it is easier to conditionalize the implementation of the
synchronization primitives than a zillion calls to said primitives.
My most humble recommendation is that the V4_THREADING be yanked from
the FB 2 code tree.
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376
[Non-text portions of this message have been removed]