down...
Printable View
down...
strange...
charm...
bottom...
top!
I get a little quarky now and then.
By the way, thanks for your help on the expression evaluators. RPN was exactly what I needed.
In retrospect, I was trying to overcomplicate something, but it was because I was ignorant on the subject.
That RPN stuff is cool to work with!
Back in the day we used this stuff in commercial products - didn't have SQL to rely on. Had to make our own database!
Foul language. Banned!Quote:
Nevermind the bollocks
Egad! :eek:Quote:
Originally Posted by FunkyDexter
Its a facist regime;)
Back in my day we hand built our databases from baling wire, string and lint.
P.S. Those are not acronyms.
What flavor is Juicy Fruit Gum?
Is the gum for when the baling wire, string and lint doesn't work?
I use JsonLint all the time
http://jsonlint.com/
I'd guess at a vanilla/banana/crack-cocaine flavor.Quote:
Originally Posted by Gruff
Hah!
Re: old database
You could use chicken coop wire in a pinch.
The hole size was perfect for filtering out unwanted data.
You can see where ACCESS came from ;)
szlamany, how would you write your own database using RPN in theory?
The work you did so far was all about literals in the equations - getting run through your execute code so a final product could be arrived at.
You just need to support other then a literal - a reference to a field name would work. Then when you run your execute code and you come across a non-literal item, your code finds that value with whatever method works (like getting that field from a row in a dataset).
I posted a link back in that other thread to the set of "operators" and such that we supported back in my DEC PDP and VAX days. Some of the functions talked to our "data layer".
Here's a screen shot of a VAX utility for defining a database record. Code I wrote back in the 1980's. Still have some customers with VAX's that run. I'll post a series of screen shots to show you...