call -151, not call 151, though it was certainly possible for call 151 to work under certain conditions.
The 65C02 machines were nice because of the assembler. The ][ had it too (*F666G) but the ][+ and first model//e lacked it. Shame.:( I learned a lot of 65C02 by poking around in mini-assembler.
The original ][ had Steve Wozniak's BASIC which was limited but very well coded. It had a minor bug that produced the wrong error message in certain circumstances, not bad for being HAND-ASSEMBLED.
Then they ditched it for that pile known as Applesoft, the mutant brother of the Commodore BASIC, which like the Commodore BASIC was written at M$. It was a more powerful BASIC, sure, but it was considered bloated (10K vs. 6K) and sluggish, and it had a number of bugs. Sound familiar?
They tried to get me to use their poisoned servers, and as soon as I found out (btw, they DO report nxdomain, along with their error handling servers), I went back to the old ones.
The poisoned ones were 68.237.161.12 (nsnyny01.verizon.net) and 71.250.0.12 (nsnwrk01.verizon.net), and the unpoisoned ones are 151.202.0.85 and 151.203.0.85.
THIS! I thought I was alone in thinking GNU software was a sluggish bloated mess compared to BSD. If I weren't concerned about what would happen if I ripped out the GNU underpinnings (coreutils etc.) from my Debian installation I prolly would replace more of it with BSD code.
I do some extremely evil stuff with Word that, when I try to do it in OOo, makes me want to throw my machine out a window. Stuff like associating separate headers with separate sections, instead of doing it through some convoluted style sheet system and hidden text and all sorts of nonintuitive bullshit.
Sorry, guys, OOo is good for what I need 95% of the time, but 95% isn't enough. I keep Word around for the other 5. (mind j00 I still use OOo the other 95)
The buffer is 2048 bytes, and it's always good to leave slack. (I needed a buffer that was large but not too large.)
As for the & thing - it's better safe than sorry. I use parentheses EVERYWHERE.
e.g., (not real code) if (!((foo==20)||(bar>65))) { grill(); }
The obscurity is the abuse of the trinary operator (I do this a lot).
I use short, but typically explanatory variable names, though for throwaway variables I tend to use i j k etc.
In one case I have "eolv" (end of line verbose), "suppress" (suppress certain errors), "tabv" (expands tabs, for tab verbose), "verbose" (expands control chars), "unbuf" (unbuffered i/o), "c" (char iterator), "synerr" (syntax error), "pnam" (program name - it's assigned right away to argv[0]), "travel" (int interator), "start" (first argument to process). A comment lists the switches and what they do briefly, one other comment explains a vagueness in the spec. No need much for comments, "if (verbose)" speaks for itself.
If I do something weird or non-obvious I'll usually explain it (if tersely). Comments in my code? Pretty limited, really. If I feel a program is more or less self-explanatory, it might not really have any comments.
The uname code contains a single comment stating what switches do what and what is default, and no further comments.
The basename code has a single comment also, explaining that behavior isn't clearly defined and that I chose to implement it a certain way.
The code is occasionally obscure, e.g., strftime(sfmt,2047,argc>ckprm?&(argv[ckprm][1]):"%a %b %e %H:%M:%S %Z %Y",&tm); but that happens more because I'm a terse coder than because I'm trying to be obscure.
Now YT, bring back xenutv1 (since you cancelled it because of the original xenutv that you cancelled because of a Viacom complaint) and I might consider calling it even.
Been using PINE/ALPINE for years and I'm doing just fine.
It's gotten a bit of an html renderer since becoming ALPINE. Still, though, it's fast enough and light enough for me. (I too believe in "e-mail is meant to be text only, bar attachments")
Slashdot Mirror
Ebichu fans?
-uso.
Time Warner's boxes are still Scientific Atlanta up here.
Why, oh why, must cable use different frequency from aerial? Oh yeah, so they can rent you their box for $10 a month. Fucking highway robbery.
-uso.
And of course when Linux is finally desktop-ready they'll see it as too mainstream for them and move on to BSD, Minix or Solaris.
As some already have.
-uso.
Most places here don't even sell pseudoephedrine anymore but only phenylepherine.
-uso.
call -151, not call 151, though it was certainly possible for call 151 to work under certain conditions.
The 65C02 machines were nice because of the assembler. The ][ had it too (*F666G) but the ][+ and first model //e lacked it. Shame. :( I learned a lot of 65C02 by poking around in mini-assembler.
-uso.
Hehe, all I got in my //e is a Z80 card...and the stock 128K (it's the Platinum model)
-uso.
The original ][ had Steve Wozniak's BASIC which was limited but very well coded. It had a minor bug that produced the wrong error message in certain circumstances, not bad for being HAND-ASSEMBLED.
Then they ditched it for that pile known as Applesoft, the mutant brother of the Commodore BASIC, which like the Commodore BASIC was written at M$. It was a more powerful BASIC, sure, but it was considered bloated (10K vs. 6K) and sluggish, and it had a number of bugs. Sound familiar?
-uso.
With a Ramworks, the Apple //e could handle 3 MB of RAM. In theory it could handle 16 MB, but the documentation said it was limited to 48 banks.
-uso.
They work for me... you know any better ones?
-uso.
They tried to get me to use their poisoned servers, and as soon as I found out (btw, they DO report nxdomain, along with their error handling servers), I went back to the old ones.
The poisoned ones were 68.237.161.12 (nsnyny01.verizon.net) and 71.250.0.12 (nsnwrk01.verizon.net), and the unpoisoned ones are 151.202.0.85 and 151.203.0.85.
-uso.
I actually preferred Coke II (its name in the early 90s).
-uso.
I have no qualms putting yellow mustard on French fries.
-uso.
THIS! I thought I was alone in thinking GNU software was a sluggish bloated mess compared to BSD. If I weren't concerned about what would happen if I ripped out the GNU underpinnings (coreutils etc.) from my Debian installation I prolly would replace more of it with BSD code.
-uso.
Ugh. I still use byacc as my yacc of choice because Bison, like all GNUware, is bloated.
-uso.
People wonder why the hell I need a 23 point font for IRC when I have 20/15 vision. I just say I want to keep it that way.
-uso.
I do some extremely evil stuff with Word that, when I try to do it in OOo, makes me want to throw my machine out a window. Stuff like associating separate headers with separate sections, instead of doing it through some convoluted style sheet system and hidden text and all sorts of nonintuitive bullshit.
Sorry, guys, OOo is good for what I need 95% of the time, but 95% isn't enough. I keep Word around for the other 5. (mind j00 I still use OOo the other 95)
-uso.
The buffer is 2048 bytes, and it's always good to leave slack. (I needed a buffer that was large but not too large.)
As for the & thing - it's better safe than sorry. I use parentheses EVERYWHERE.
e.g., (not real code) if (!((foo==20)||(bar>65))) { grill(); }
The obscurity is the abuse of the trinary operator (I do this a lot).
I use short, but typically explanatory variable names, though for throwaway variables I tend to use i j k etc.
In one case I have "eolv" (end of line verbose), "suppress" (suppress certain errors), "tabv" (expands tabs, for tab verbose), "verbose" (expands control chars), "unbuf" (unbuffered i/o), "c" (char iterator), "synerr" (syntax error), "pnam" (program name - it's assigned right away to argv[0]), "travel" (int interator), "start" (first argument to process). A comment lists the switches and what they do briefly, one other comment explains a vagueness in the spec. No need much for comments, "if (verbose)" speaks for itself.
-uso.
The code is occasionally obscure, e.g., strftime(sfmt,2047,argc>ckprm?&(argv[ckprm][1]):"%a %b %e %H:%M:%S %Z %Y",&tm); but that happens more because I'm a terse coder than because I'm trying to be obscure.
-uso.
ORLY now. I'm still officially a man (much to my chagrin), and I've always used landmarks to give directions.
-uso.
The actual tech of the keyboard *is* Model M. Unicomp is a spinoff of Lexmark, which got the tech when they spun off IBM.
-uso.
Now YT, bring back xenutv1 (since you cancelled it because of the original xenutv that you cancelled because of a Viacom complaint) and I might consider calling it even.
-uso.
Why would they bother? It's just a big ghetto, there's nothing to see here in Niagara Falls, NY.
-uso.
Didn't TELUS get in trouble in Canada for blocking websites critical of them?
-uso.
Been using PINE/ALPINE for years and I'm doing just fine.
It's gotten a bit of an html renderer since becoming ALPINE. Still, though, it's fast enough and light enough for me. (I too believe in "e-mail is meant to be text only, bar attachments")
-uso.
But maybe they Steam rolled the place.
*RUNS*
-uso.