- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
frist
Admin
String String String String
String String String String
Wonderful String! Marvellous String!
"Do you want Curves with that?"
Admin
trying to imagine bool curve
Admin
You mean there's an industry out there that does not approach software development that way? Pray, do tell, I shall be blowing the mould off my diseased and tear-soaked CV.
Admin
A Floating Bool curve sends the developer down the creek without a paddle
Admin
fast-paced or past-faced?
Admin
Obviously, just use a StringVariable and put JSON inside of it. Then you've got all the fun of XML and JSON together! In a bug-riddled enterprise system!
Admin
As someone who works in automotive software, I can attest that the first paragraph is correct, and that I'm not surprised by this at all.
Admin
They could have created a program creating an XML with all permutations of basic variables and each type of collection ...
Admin
Limiting the possible "generic" variations of collections in a standard does have the benefit that you could test each and assume that every service supports all of them. Otherwise your list of maps of floats to curves may not be supported by some service routing the data.
Admin
As someone who has worked with an automotive standard that got adopted by a non-automotive company (my god WHY!?) I can say that their standards are absolutely this way. At one point we discovered that the serial cable we had running to the box could not be more than a certain length, because the packets had to arrive within a minuscule time period of when they were sent (the only testing had been using a 2ft cable on someone's desk). Our USB connection had to be direct to the computer, using a USB hub/Active Cable/cable longer than 10 feet screwed up addressing and caused the box to register itself as a mouse (and watching data come in and get resolved to mouse movements/clicks made very... interesting things happen to the computer.
Admin
I'm guessing both.
Admin
I would love to see a video of that!
Admin
FloatFloatFloatMapVariable sounds like we're on a sinking ship.
Admin
In before ....
that was the XML output of the program generating all the permutations
Admin
DanceDanceRevolutionVariable
Admin
You New Romantic, Ulysses.
Admin
what the hell is a String String Curve????
Admin
Why do the 'Map' types seem to have three type arguments? In (e.g.) 'FloatStringIntMapVariable', which of {float, string, int} is the key type, which one is the value type, and what is the extra one for?
Admin
What, no love for ASN.1?
Admin
Previous versions of Windows used to detect any serial input during boot as a serial mouse. The solutions were to not have any serial input at boot time, to mess with the registry, or to avoid using versions of Windows older than about Win 8.
https://support.microsoft.com/en-us/help/283063/serial-device-may-be-detected-as-a-serial-mouse-in-windows-2000
Admin
Yes, automotive standards are weird. The best example is the nice "ODB-2" connector that exists in modern (post 1995 I believe) vehicles. You see there are TWO standard protocols used here. One uses one set of pins, and another a couple of different ones. Vehicle makers pick onr or the other. The unlucky scanner vendors need to support BOTH. Thankfully the connector is "standard", but only to the automotive industry.
Of course if computer people did it (like the IETF guys) they would properly use a nice serial port (most likely an DE-9 connector) and define nice logic levels. Another alternative might be something like MIDI which also was defined by someone who knew what they were doing.
If you look at vehicles, about the only electrical standard is that they run on is 12 volt batteries (which is about 13.5 in a running vehicle). Good luck with anything after that.
Admin
I even expunged all mention of ASN.1 from my dev profile/cv. Along with a few other tehcnologies I know but have no wish at all to work with. :P
Admin
String String with string, String string string float and string. Or map boolean variable curve factory, with generic template abstraction and string.
Admin
You can see at a first glance that this schema can't be right. It simply can't.
What did they do to the wonderful smooth parabola it was intended to be?
(Btw, I didn't expect a customer not understanding or even knowing their own requirements was not so specific to the automotive industry.)
And what about StringStringStringMapStringStringFloatMapMatrixVariable? According to my experience with this kind of stuff, something like this will be necessary (maybe only temporary) in the near future.
Admin
Well, I guess that's better than NT 4.0, which had a single BOOT.INI switch to disable serial mouse support. (As if you'd need to support a serial mouse and another serial device...)
Admin
BadgerBadgerBadgerMushroomMap variable
Admin
There were 6V vehicles back in the day (eg the VW Beetle) and most trucks run 24V so the 12V "standard" is as standard as anything else! Even then, what is the standard connector for this power source?
I remember in my parents' 1976 Ford Falcon its cigarette lighter was bigger than other cars so no plugin accessories would fit.
Admin
What about StringIntBoolString? It's only got a little bit of String...
Admin
Not so much serial mouse and other serial device, no. It was to stop serial mouse detection from watching the serial port and thinking that bytes X,Y,Z that were received from the other device were in fact from a mouse.
Admin
Had a similar problem with another global industry body, they adopted a standard designed by a particular large company whose name rhymes with Doortel. "Look at our perfect solution, you should all adopt it". Turns out this had never been tested outside a LAN, with close to zero latency and zero packet loss. As soon as it was run outside a perfect-conditions LAN, it fell over catastrophically. This is why the first version of the protocol was "version 2", since what was supposed to be version 1 didn't actually work in the real world.
Admin
My bad, I thought it disabled detection on all ports, but in fact it was also configurable.