its probably all of us to a point, though some are worse about it than others
I see your problem Mike
call(reply #1);
Also "no_one_gets_it" should be declared as "volatile rtfm".
Rob
I think the use of "volatile" there is just so profound.
Bravo.
old thread, but wanted to add two more.
OP : "I tried connecing a 12v relay to a PWM pin and now by UNO smells really bad "
response : create a hand sketch, scan it an post a copy of your schematic.
response #2 : post your code.
response #3 : post a link to your relay
maybe this is forum law #3 ?
The answers are only as good as the question.
a corollary is that you have to know the technology in order to ask the right question.
and that implies that if you knew the technology, you might not be asking the question......
I think Tom George has the number one law of the forums well thought out already: Everything runs on smoke, let the smoke out, it stops running.
I mean, really, what more do you need to know?
Qdeathstar:
I mean, really, what more do you need to know?
How to get the smoke back inside !
...R
But first you need to know how to capture the smoke.
Weedpharma
weedpharma:
But first you need to know how to capture the smoke.
Jeez, that's the easy bit - just inhale it.
...R
Robin2:
Jeez, that's the easy bit - just inhale it....R
I think y'all have been doing too much of that, around some substances of questionable legality.
PaulS:
substances of questionable legality.
Never touched the stuff - not even once (in any form).
Never smoked a legit cigarette either.
...R
It's doubly sure that the issue is in the project when the person who finds the compiler bug states that they can't be wrong because they have been using the language for 50+ years!
ChrisTenone:
when the person who finds the compiler bug states that they can't be wrong because they have been using the language for 50+ years!
Wow, a person from the future!
C was originally developed by Dennis Ritchie between 1969 and 1973 at Bell Labs
I thought the same thing myself! To be fair, the qp did have some weasel words, but the number 50+ was mentioned, and purpose was to impress that they had more experience than anyone else who could be reading the post.
They were wrong of course: a simple typo had been missed - yet quoted - several times.
ps, this is recent. Like yesterday.
if you're new here and you post a project you make, it isn't yours, you stole it from a website, and it's a piece of shit either way.
And even if it is good, once you post it on Instructables, it's no longer worth debugging or even looking at.
My take on instructables is that it should be for completed projects which have been debugged and therefore don't need further debugging. If you can post a chunk of undebugged/non-working code on there, it's hardly worth the name "instructable" unless the idea is to post stuff which demonstrates how not to do things.
Pete
el_supremo:
My take on instructables is that it should be for completed projects which have been debugged and therefore don't need further debugging. If you can post a chunk of undebugged/non-working code on there, it's hardly worth the name "instructable" unless the idea is to post stuff which demonstrates how not to do things.Pete
The code works just fine. Sure, there could be some fixes, but it works. Nobody is perfect. Well I'm not clearly not, anyway.
chummer1010:
if you're new here and you post a project you make, it isn't yours, you stole it from a website, and it's a piece of shit either way.And even if it is good, once you post it on Instructables, it's no longer worth debugging or even looking at.
What prompted this and Reply #57?
What code are you talking about that "works just fine"?
Just because someone is new to this Forum does not mean they know nothing about programming.
...R
@el_supremo, thanks for the link.
@chummer1010, you could easily have avoided a lot of confusion if you had explained in your first post in that Thread that it was you who had created the Instructables project.
...R