Subject:
|
Re: signals / legOS internals
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Wed, 23 Jun 1999 19:31:31 GMT
|
Viewed:
|
1136 times
|
| |
|
|
On Wed, 23 Jun 1999, Ola Liljedahl wrote:
> Why signals?!?
>
> Unix-style asynchronous signals is the last feature I would
> ever want to implement or use. Brain-dead and very dangerous
> "feature". As you write; "The problem is that a signal can
> happen at any time". You shouldn't pass this problem on to the
> application writer, it should be handled in the kernel and
> reliable (synchronous) mechanisms (for instance semaphores,
> message queues or OSE style message passing) should be presented
> to the application.
An asynchronous signal models a hardware interrupt. There are times when
that is the appropriate interface. There are times when other interfaces
are less error prone and are easier to write correctly. Frequently using
only synchronous communication involves creating additional buffer threads.
The additional overhead for such an approach is not always justified.
John A. Tamplin Traveller Information Services
jat@LiveOnTheNet.COM 2104 West Ferry Way
256/705-7007 - FAX 256/705-7100 Huntsville, AL 35801
|
|
Message has 1 Reply:
 | | Re: signals / legOS internals
|
| (...) But hardware interrupts schedule a different context (the interrupt process or ISR) from the one already executing. A Unix-style signal asynchronously signal interrupts the executing process and jumps to a different location in the code that (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
Message is in Reply To:
| | Re: signals / legOS internals
|
| (...) Why signals?!? Unix-style asynchronous signals is the last feature I would ever want to implement or use. Brain-dead and very dangerous "feature". As you write; "The problem is that a signal can happen at any time". You shouldn't pass this (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
32 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
