|
Well, I've seen your construction before.
It's known by many names, such as MUCK (Massively Unified Code-Key), OTLT (One true lookup table) and EAV (Entity Attribute Value) for example.
And it's generally not a good idea.
I won't bore you with my own experiences since I saw the problems in time. So read this [^] instead.
<edit>And another one[^]</edit>
|
|
|
|
|
I really like your signature... It is true! Evil must be defeated! (I happen to be writing a book on morality currently.)
Very cute article, but since I am all those roles, it should work out... If only I could get Jack (my personality #3 - handles database code) to quit just repeating "burn them, burn them all" again and again... but he always does that anyway.
I do understand the objection, but my database is pretty well set.... mostly varchar, date and some int keys. It's the conversions between them that is an issue. When parsing from scraped PDF or HTML, I have to have the the string literal indicating what I am scraping such as "First Name:" or "Date of Birth:" and the value scraped, so there are two strings in the c_Field object. Then there is the name in the database "FirstName" and "DOB" with their values "Chucky" and "01/10/2017". Then the length in the Db and the data type. Add OutputCaption, DataSource and Error and you have a description of a data member that can be put into a data base or... use reflection to populate the data members of the class (with or without the same name as in the Db)... since there is reason for me to serialize this to JSON. It is parsed on one machine with no good connection to the machine that consumes it. Oh yah, it becomes part of an HTML page displayed in a Win Form Web Browser Control.
Partly it seems sort of cool too. Besides, the same stuff that keeps my MAR Clap at bay holds off the fever. Really, if that isn't enough explanation for why this is difficult, realize it's for my wife.
|
|
|
|
|
Well, conversions shouldn't be a very big problem. That's just a lot of work. 
Your serious problems start when you need to put relations and constraints between the different entities.
But if you don't need relations and it's only a common lookup table where you have proper checks for your data in place, then go for it.
|
|
|
|
|
|
And he obviously edits Wikipedia pages: Universaw Synchronous/Asynchronous Receiver/Transmitter - Wikipedia[^]
Quote: The USART's synchronous capabiwities were primariwy intended to support synchronous protocows wike IBM's Synchronous transmit-receive (STR), Binary Synchronous Communications (BSC), Synchronous Data Link Controw (SDLC), and de ISO-standard High-Levew Data Link Controw (HDLC) synchronous wink-wayer protocows, which were used wif synchronous voice-freqwency modems.
By the way, does anyone happen to know a USART besides the Intel 8251 or the Zilog types?
Edit: I'm glad I posted a quote from the page. It's now back to normal. Did anyone edit it?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
modified 10-Jan-17 8:58am.
|
|
|
|
|
|
Microcontrollers are not an option. I want to interface PS/2 keyboard and mouse or possibly SPI EEPROMs to an old 8 bit processor. The Intel 8251 looks about right and probably could read input from a PS/2 device, but not send anything to them. SPI also would not be a problem if I could figure out wether or not it can use the same serial clock output for sending and receiving.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
This might become slightly off-topic here in the lounge:
Does it care how the interface device is working internally (dedicated interface chip, or programmed FPGA or micro controller)?
SPI and I2C can be implemented in software (done that for I2C). For both, the master is generating the clock used for sending and receiving (I2C knows also a feature called "clock stretching" where the slave can block the clock to inform the master that it is not yet ready to send / receive the next bit).
|
|
|
|
|
The problem is the old architecture. I need I/O chips that signal incoming data by raising an interrupt and stay off the data bus until the processor comes and reads the data register. All microcontroller solutions I have seen had some trouble with that last part, as they could not tri-state their I/O pins and put the data on the bus when the read signal comes. Otherwise I would not mind using a microcontroller for the PS/2 ports.
Another option would be to use standard UARTs and use them to attach USB keyboard and mouse with a converter inbetween. Ugly, but it would work.
As for the serial EEPROMs: Bit banging has a long tradition on this particular computer, but it's quite slow. We used to bit bang RS232 to attach terminals. The old programs ran at 'safe' 300 baud, but with a little tweaking we already reached up to 2400 baud. At a slightly higher clock frequency 4800 baud have been reached and (without having tried it yet) 9600 baud may also be possible at the maximum clock frequency. A bit banged SPI or I2C interface would perform no better than that.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
I grow up with 8-bit controllers (8080, 8085, 8051, Z80, 6502) and have written programs for all of them. But that is more than 30 years ago.
Regarding the tri-state:
Just let the micro controller ports be inputs (high impedance) and switch to output mode when data should be put onto the bus.
Then you might also use the micro to interface with serial SPI or I2C EEPROMs using the corresponding hardware interface. But this might require some delay between reading and writing multiple bytes to finish serial communication and write delays.
|
|
|
|
|
Jochen Arndt wrote: I grow up with 8-bit controllers (8080, 8085, 8051, Z80, 6502)
The old CDP1802 processor fits well into that collection.
Jochen Arndt wrote: But that is more than 30 years ago.
Exactly. It's my first computer and the keyboards are worn out. Real key switches are hard to get and some that fit onto the old boards are almost impossible to find. I'm going to leave the old computer as it is and just build a new one, but I will need a solution for interfacing a more modern keyboard and a mouse.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
CDP1802 wrote: Edit: I'm glad I posted a quote from the page. It's now back to normal. Did anyone edit it?
The page wasn't edited since the 1st of November, 2016... You have a virus
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
A virus that only messes things up one time and then disappears?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
CDP1802 wrote: A virus that only messes things up one time and then disappears?
It was a good-will-warning... 
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
It might help if you notice that you haven't actually linked to Wikipedia But rather to: "http://wikien4.appspot.com/wiki/USART"
|
|
|
|
|
Overlooked that. Thanks. And thanks, Google, for sending me there from the top of the list.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Be quiet!!! You spoil the fun!!!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Sorry 
|
|
|
|
|
Ive worked with Atmel, now Microchip Technology USART. Probably similar in most MPUs.
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
If markdown is 'programming' then slap my thigh and call me Beryl.
I'm writing a rather long README.md for some inhouse tools we user for our software. I want a single file that everyone [well the other four people for now] can go to with all the syntax and explanations. The one thing that is now haunting me is putting in links. Why you cry Vilmos?
What the doc looks like is:
## This
### Syntax
### Example
## That
### Syntax
### Example
Because the headings have the same text they end up with the same id and I can't link to them. Anyone know what I should do. Our repos are on github if that will make a difference.
EDIT -
I can find documentation on how to use bloody emojis but put an id for a link into the doc? No bloody way!
veni bibi saltavi
|
|
|
|
|
Give'em a plain text file and tell them to like it.
Tired of cottonin' to these whippersnappers.
|
|
|
|
|
I'd almost agree if it wasn't for the fact that I like linkies!
veni bibi saltavi
|
|
|
|
|
Use HTML?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Can't you manually name the pieces of heading with something like
[EX01]
## Something
### Old
[EX02]
## Something
### New ?
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
## This
### <a name="this-syntax"></a> Syntax
### <a name="this-example"></a> Example
## That
### <a name="that-syntax"></a> Syntax
### <a name="that-example"></a> Example
To link to these:
Take me to [This/Syntax](#this-syntax)
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
