Whats wrong with ENGLISH - I cant find much on this thread and even less out in the streets where i live?
Sorry, reminds me of a joke.For those aspiring to writing games, I'd suggest that they learnt 6502 assembler on a VIC-20; to learn how to write tight, functional code to produce addictive games with intense game-play. In 3.5Kb of RAM. Then let em have a C64..
Its always good to find another exponent of the seldom used Engineers Next Great Learning Incline Shit Help language, or ENGLISH, as you so cunningly put it. For those that dont know it, heres a snippet:Whats wrong with ENGLISH - I cant find much on this thread and even less out in the streets where i live?
Forgive me, but my memorys fading now (seriously, I left the 1K chips on the windowsill on a sunny day and I think theyre buggered), but I think you are using the predecessor YANK, or Your Angry Nipples Kaboom!, with its line numbers, rather than ENGLISH. Heres the newer code with a few additions:Allow me to demonstrate the concept of inheritance (and plagiarism) with a distinct 80s BASIC flavour:
10 REM Shiny Happy People Holding Hands
20 REM Sub-routine BAOR Block Bang
30 Four eyed = 1 to 20 DM
40 ...Go to clinic afterwards
50 Next I
60 IF INSTR$("MONTH OF YEAR", "R") GOTO 30 ELSE PRINT "**** IT, EXERCISE SEASON"
Well, most computers have at least one ... but don't forget that was a Text Only Window in them days! Most of my mainframe graphics was done using characters (even coded my own routines - Bresenham ring a bell with anyone?) never mind the NASCOM. IIRC, the NASCOM 1 used 1 KBi RAM for 'video'; not all of it was used for the display (16 lines of 48 characters?) as the video hardware couldn't scan quickly enough to allow for flyback (or something like that). For some reason that vastly bemused me, the video driver used a block shift to scroll all of the characters, which meant that the 256 'invisible' bytes were effectively unusable (without subtle use of indirection). So I rewrote the scrolling routine to shift smaller blocks and at the same time provided the abililty to define 16 text 'windows' onto the screen - they necessarily shared the same 'space', as 'proper' window handling would have taken more memory than I had! Also, bear in mind that I was a physics undergrad and didn't know about 'windows' - it just seemed like a good idea to help manage my display (which was my B&W TV, in case anybody's getting fancy ideas about HD, DeepColor, touch-sensitive devices, and 'non-volatile mass storage' was my tape-recorder).The Nascom had windows??? I remember it, and remember one turning up at the local computer club. Have ancient issues of PCW, Computing Today, which features it... must go dig them out.
I signed up for a Pascal class to get access to mainframe (Cyber 72?) through a (dumb) VDU and then managed to find, ahem, 'creative' ways of staying on the system.I expected nothing less (cards). All programs to be submitted to a data entry operator, for batch processing. Results will be returned with a 48hr turn around. Paper tape may be used for local storage during "off-line" development if a dumb terminal is available.
If word of that had ever got out ...NO WAY! A !!!FEMALE!!!
Most? All? of them were. The CBM's "video display" was simply 1024 memory locations that were directly displayed. Screen manipulation was nothing more than changing the contents of a given location.Well, most computers have at least one ... but don't forget that was a Text Only Window in them days!
The bane of just about every 8-bit machine - certainly those that only offered text-mode display. The TRS-80 was similar, 16x64, and a "graphics" mode that simply treated each character as a 2x4 cell, iirc. But the slow scan limitation was often used to good effect on the PET and TRS 80 to "flash" the screen.the NASCOM 1 used 1 KBi RAM for 'video'; not all of it was used for the display (16 lines of 48 characters?) as the video hardware couldn't scan quickly enough to allow for flyback (or something like that).
Love a good hack At RECIS we had an HEO whose role was to QA all work (SSADM and programs). Most of the 'programming' was turnkey application, e.g written in Supercal macros or DBASE/Paradox. His pet response when faced with "press any key to continue" was to press the CTRL, SHIFT, ESC, FUNCTION keys, which of course did nothing, then fail the program with a cutting remark. Even the SNCOs didn't like submitting work. So I wrote a TSR to scan the keyboard interrupt, then launch a DOS pop-up with "**** off, Speed" if any of those keys were pressed. Took a Supercalc 'program' in, after 'sabotaging' his PC... and waited. He loved it, thought it was very amusing, and I never had to submit to QA again.For some reason that vastly bemused me... 'proper' window handling would have taken more memory than
Ahhhh, ditto. After getting used to "monitors" at SCBM (local business shop where I helped out), my mum bought me a Video Genie. My display was a white portable B&W TV, sat on a chair, whilst I sat on the bed with my VG perched on my knees... and played Galaxy Invasion for hours. Still have it, and the TRS-80 I picked up years later (with real Tandy monitor), and a load of tapes....which was my B&W TV, in case anybody's getting fancy ideas about HD, DeepColor, touch-sensitive devices, and 'non-volatile mass storage' was my tape-recorder).
You had a VDU? At school, we had a remote teletype terminal that was fuckin HUGE. Even know I reckon it wasn't much smaller than a 28" CRT TV, with an awful keyboard; the keys were cyclindrical in appearance, and needed to forcefully pressed down. The "display" was a roll of paper, and I still have a SNOOPY printout from it. Local storage was paper tape. Connected to the local college ICL2903 by acoustic coupler. Although it didn't take Dave G and I long to 'hack' it - probably because there was no real security other obscurity - and gain sysadmin privs. First experience of a VDU was a PET 2001 (original model with mickey mouse chicklet keyboard and white VDU) in town, playing "star trek" and scrolling the screen faster than one could read when LISTing a program.... the scroll speed is tame now... but I was start struck.. and have one in the loft.I signed up for a Pascal class to get access to mainframe (Cyber 72?) through a (dumb) VDU and then managed to find, ahem, 'creative' ways of staying on the system.
Too true. You can write sh!te software in any language, just like you can write decent software in most of them (I'll grant you that ML is a sod). The indicator is whether the person who takes over maintenance of your code can understand, trust, and modify it; or whether they rewrite it at the first opportunity. Do you want to be a programmer, or a software engineer? There's a difference...... it would depend on what their ultimate goals in programming were...
Living proof of "GOTO considered harmful"ScouseD said:Goto field medic
...Sub-routine: Get aspirin .and. fight
Sure. Start your own thread. There's potentially enough milage in the current subject for a bit a straight and level before manoeuvring into that big a meander - the first half of such a thread would be devoted to determining what you mean by 'think'.Will there ever be artificial intelligence? Machines that can think and write their own language? Let's have that one eh...
Been done. Skynet is an early example.Perhaps they will collect all the data available and work in government...cool.
Again, separate thread stuff. Ask an adult to show you how if you can't work it out.Mmmm...I wonder if there is there a finite amount of information in the universe ?
A Consultant? Ah. That explains much ... not everything, but much. I refer to an earlier message in this thread.I'll get back to my simple Excel formulas now... I'm a Procurement Consultant
But you're happy enough to insult us on the equipment we provide!not a bloody geek!
I vaguely remember those. When did Personal Computer World first appear ... just a minute, I must say the magic mantra ...Just for excognito, I have dug out some old Computing Today and Micro Computer Printout mags from Oct-Dec 1981...
<embed src="DvorakNewWorldSymphonyHovisAd.wav" autostart=true loop=true>I'd suggest that they learnt 6502 assembler on a VIC-20;
I have a copy of PCW from 1979 still... but my fave is the August 1985 copy, in which Guy Kewney (RIP) reviewed the C= Amiga, and I learned what true love really was... hook, line, sinker. I think I might have PE from the late 70s or early 80s somewhere, and some Military Modelling and Angling Times (when AT was a real paper). Whoops, off-topic and venturing into sad anorak territoryI vaguely remember those. When did Personal Computer World first appear ... just a minute, I must say the magic mantra ...
Feb 78. That's the one that rings more bells in the empty attic of my mind.
My first foray into computing was with something I built from Wireless World or Practical Electronics(??) - an Analog Computer. Luckily, we'd just started calculus at school, so at least I had a vague idea what a 'differentiator' and 'integrator' were supposed to do.