Hi all you programmer people
I wnder if some kind soul can help me?
I have a project on the go which involves 10 sequencial logic level outputs with presetable times on each of the output pins
I imagine it would be very easy to do with a chip if you know how. Unfortunately I don't know even basic programming so I was hoping that someone would take up the challenge.
I don't know what the times are yet so I would need very simple instructions as to how to set and change them.
Once the correct times are set they never need changing I have access to a programmer so have no problem with the hardware
I know programming is easy but i am very busy and don't have time. Obviously, No doubt I could learn how to do the programming, I simply don't have the time. You people know and like chalenges. here is my chalenge for you.
Thanks for any help
Mike
Do you remember suggesting a while ago that people like me were lazy dogs because I used the large memory model?
I guess what you refer to is: I have seen "I use large so I do not have to worry about space" which I read as "I use large because I am a lazy dog" please note the bold portion which clearly indicates 'opinion'
Do note the the 'lazy dog' is not the one that use 'large' but the one that use 'large' in order not to worry about space.
If anyone has a qualified reason (not just "not to worry"), as seen by those that actually read the whole story, I do not see how it applies, unmless, of course, 'not to worry' happens to be your reason.
Anything with a qualified reason will, of course be a qualified decision, not just "I'm too lazy".
I could, of course, stop worrying and tell my employer that we need to use a processor that is twice as fast with twice the memory. That, however is a very unlikely event.
Regardless, I do believe that the use of 'large' in most cases is unjustified.
Erik
"Do note the the 'lazy dog' is not the one that use 'large' but the one that use 'large' in order not to worry about space."
Unfortunately, that was not the way the posts in the original thread actually read.
I will just remind you: What I saw as the problem was someone posting opinions in a manner that appeared to be authoritative. An action that would probably lead to less experienced people thinking that these opinions are desirable targets; thus limiting their armoury of methods open to them when developing code.
And taking Jonny Windapeg advice, I will now say this:
<NotWrappedInPinkCotton>
It is my opinion that the poster whose posts need curtailing most is the ardent moniker hater himself (aka Mr Ego).
</NotWrappedInPinkCotton>