M.L. wrote:
>> > Anyway, if you take the concept of task switching, add a few primitives
>> > like
>> > timers, inter-process communications (mutex, semaphore, queue, etc.) 
>> > you
>> > have a basic operating system. If you add a standard format for loading
>> > executables, memory protection, and resource management, you're 
>> > half-way
>> > to
>> > a decent desktop operating system.
>>
>> I don't get it. What is it with people's fascination with reinventing the
>> wheel? :)
>>
>
> Because the "wheel" is usually a full blown engine with transmission that
> weighs 2500 pounds and you're trying to fit it in a 1cm^3 box. There's
> nothing wrong with writing your own code. If nobody reinvented the wheel
> we'd all be technicians soldering black boxes together.

Martin, the problem with your guys' responses is that they make a lot of 
sense in a vacuum, but not in the situation we're discussing.

Is SW trying to build a home automation system, or is he trying to learn how 
to design custom token-based protocols and write PIC-based desktop operating 
systems?

Using someone else's code does not preclude you from writing your own code.

Vitaliy 

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist