bulletin blues
Lifetime Supporting Member
As an electrician, I could probably hook this up with as little as 120 jumpers and 25 well tuned pnuematic timers, Keep It Simple. Y'all overcomplicate things.
25' and 8m/26'. I buy them anytime they:re on sale. I have no idea how many I now own but for sure too many.My favorite tape measure is a 16’ Stanley fat max.
I’m more talking about all of the variable declarations and such at the top while the LAD was allowed to reference global variable registers.
Sure...it’s all equal for small/trivial examples. Everything is fast for small n too...
Sorry, the "Turing complete" reference was intended only to make the point that products written in either LAD or ST behave in the same way; any differences in execution would be meaningless. I'm not suggesting anyone code in Logo.I’m not sure it helps to point out that they’re all Turing complete.
As an electrician, I could probably hook this up with as little as 120 jumpers and 25 well tuned pnuematic timers, Keep It Simple. Y'all overcomplicate things.
Sorry, I was not trying to suggest code golf as a metric; I know the declarations are hidden/separate in LAD. When I look at that ST-ish code, even if I cut it down, I still see roughly the same "instruction" count i.e. baker's dozen.
Sorry, the "Turing complete" reference was intended only to make the point that products written in either LAD or ST behave in the same way; any differences in execution would be meaningless. I'm not suggesting anyone code in Logo.
My own personal preference would depend on the application. For example, PLCs are a hobby for me and my real job in procedural/OO* languages, so ST would be a step back, while LAD is novel. But those are purely subjective metrics; they do not suggest to me in the least that one is better than the other. If I had an actual project, I would likely go with ST for the simple reason that its textual nature would be easier to integrate with Git, specifically the [git diff] command, and also because I was more familiar with the style. For this particular task, the OP asked for ladder. Those are all subjective or application-specific reasons.
To state that LAD is obsolete or that people are obsessed*** with it, because the miracle of ST exists, does not make any sense; at a minimum it is wrong.
* I think those are the right terms
** although there was a recent thread about integrating LAD into Git
*** Certainly some are one-trick ponies, but the circus (industry) is big enough that it does not matter.
P.S. the C version has a bug and will not work as written.
*For anyone interested, TwinCAT has IEC with OO extensions, function passing (IIRC), runtime memory allocation, and recursive functions (have to use pointers) (and it’s free)
Yeah, I noticed your "least worst" description.
woo hoo, now that's interesting (subjectively, to me )
...
So again thank you soo much!
I once applied for a job with a large company ...
25' and 8m/26'. I buy them anytime they:re on sale. I have no idea how many I now own but for sure too many.
Way too big, they are too hard to fold in half when I need to divide a length