| To: | gasbichl@informatik.uni-tuebingen.de |
|---|---|
| Subject: | Re: [Scsh-hackers] crypt issues |
| From: | shivers@cc.gatech.edu |
| Date: | Tue, 13 Feb 2001 12:06:40 -0500 |
| Cc: | scsh-hackers@lists.sourceforge.net |
| List-id: | Discussion among the implementors <scsh-hackers.lists.sourceforge.net> |
| Reply-to: | shivers@cc.gatech.edu |
| Sender: | scsh-hackers-admin@lists.sourceforge.net |
Olin> I also grumpily note crypt(3) isn't thread safe, hence would require
Olin> a lock in an OS-thread implementation. Can we say this loudly in the
Olin> comments above the function?
We don't have OS-threads, so why bother?
In principle, our designs and hopefully lots of the code, would work or port
over to a true parallel system or a VM that did threads with native threads.
Besides keeping that in mind at design time, it would also be kind to mark
code with thread-reentrancy problems loudly in the sources, to help out the
guy that does that port down the line.
-Olin
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Scsh-hackers] crypt issues, Martin Gasbichler |
|---|---|
| Next by Date: | [Scsh-hackers] Language for the manual, Martin Gasbichler |
| Previous by Thread: | Re: [Scsh-hackers] crypt issues, Martin Gasbichler |
| Next by Thread: | [Scsh-hackers] Language for the manual, Martin Gasbichler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |