|
Amazon wrote: Please Note: USB Pet Rocks don't do a dang thing. Except make you smile. It did make me smile... Then I saw the price!
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
$30 for a rock?! And they think it will make anybody smile?!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Every order guaranteed to make the guy selling 'em smile!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
|
Zach, you have to be born before 1960 to appreciate this.
/ravi
|
|
|
|
|
Did you read the reviews............
|
|
|
|
|
But there's only 3 of them left.... must....resist..... darn - just 2 left!
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
|
|
|
|
|
Even better than a USB pet rock - and you can make it yourself[^]!
=========================================================
I'm an optoholic - my glass is always half full of vodka.
=========================================================
|
|
|
|
|
I think I can do better than that. I'll sell rocks without the USB cable and call them wifi-enabled...automatically pairs with your device when near it, any device for that matter, even the toaster. And only $50!
-NP
Never underestimate the creativity of the end-user.
|
|
|
|
|
Wow! Only $35 for a '70s memory.
/ravi
|
|
|
|
|
I posted yesterday[^] about someone trying to learn with archaic tools, and that lead to finding QuickC for Dos on an abandonware site. I used to love that program!
And yes, it does run in DosBox.
Good things:
1) It's quick. Compilation is slower than I remember: for a really tiny app it spends a lot of time linking. But it loads and unloads practically instantly, much, much faster than VS.
2) The help is miles better than VS. Put it like this: it works. It could use some clarification - for example strcpy doesn't tell you which is the source and which the destination.
3) 16 bit integers!
Bad things:
1) I'd forgotten how damn limited C is! And how long it takes to get anything done with standard libraries instead of a framework doing it all behind the scenes. I want my classes back!
2) Only 21 lines of code on screen at any one time, and only 80 chars wide.
3) Copy and Paste are the old style "CTRL+INS" and "SHIFT+INS" (I'd forgotten those, but they still work in Win7!)
4) Um. That's it.
Perhaps I won't use it in anger again (I mean, when am I going to need a 16 bit application?) but it brings back a lot of memories - some of them good.
Anyone else remember this one?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Loosing my control! Who's that someone? I had this on my mind yesterday, and today I am asking it!
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Not saying. Unfair to embarrass people!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
And not fair not telling people and creating a suspense!
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Chris Duncan and I used to have discussions on how good Turbo was in the day, light years ahead of uSoft.
Haven't seen any posts from him in a while, he must be busy.
New version: WinHeist Version 2.1.0
There's a fine line between crazy and free spirited and it's usually a prescription.
I'm currently unsupervised, I know it freaks me out too but the possibilities are endless.
|
|
|
|
|
I remember the days of QuickC. Remember memory models and choosing your stack size?
After learning QuickBasic I felt like a real programmer learning QuickC.
Anyway, why didn't you just use cc or gcc? They are supported on modern OSes, easier to get now and they allow you to create extremely small -- limited -- C programs using stdlib.
Even RPi Rasbian
As a matter of fact, cc is installed on RPi's Raspbian distribution and it is very easy to use to get basic "hello world" going.
Just curious about why you didn't try gcc?
|
|
|
|
|
|
No Turbo Pascal?
In college I had some classes that used VAX Pascal and others that used Turbo Pascal. My first introduction to C was with Whitesmith's C on a VAX, but later I got to use Turbo C, never Quick C.
All the C I did on paying jobs (1994-2002) was VAX or DEC C; none of those toy compilers.
|
|
|
|
|
Yes, it was a nice IDE and amazing in those days of EDLIN and Vi.
|
|
|
|
|
I still "relapse" back to BRIEF emulation on Visual Slick Edit when I want to get something complicated done quickly in a text editor.
|
|
|
|
|
Oh yes, BRIEF was brilliant. You could even go 50 line mode. The macro language was the bomb. Wonder why they never moved over to a Windows version?
|
|
|
|
|
Oh yes. I liked the C extension language (although it was a little complex). And you could set up execution of a makefile, and ...
In some ways it's still better than the editor in VS - I really miss being able to open multiple files (or even multiple views on the same file) in the "edit space" of VS. I know you can open a "second window on the same file, but it's not the same...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
It is about our memory - I used to believe that C=64 was a supercomputer, until I run an emulator on my PC a few years ago...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I know what you mean. About thirty years ago, I was working on the VDT software for a Telecoms testing suite: there were four of us in the team doing the VDT, 10 or so doing the presentation stuff at the computer end (two mainframes: one DB, one test, with integration and control via the VDT), another dozen doing the hardware interfacing to the line test equipment. Gawd knows how many managers...
And the company it was all going to work for got a suggestion from a test department employee who was fed up with the manual system. Suggesting that a ZX Spectrum could handle it pretty easily, and he had a boy who could write the code...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: Suggesting that a ZX Spectrum could handle it pretty easily And he probably was right about that part...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|