--------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F4200066 Date: 03/29/98 From: KEVIN FROST Time: 10:16pm \/To: ALL (Read 3 times) Subj: bsave/bload Does anyone out there have a parctualarly easy method of bsaving and bloading things(graphics). If so please reply. Thank you --- Platinum Xpress/Win/Wildcat5! v2.0 * Origin: Wizard's Tower, Toms River, NJ (732)-473-1933 (1:107/710) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F4200067 Date: 03/28/98 From: BILL WHITE Time: 07:00pm \/To: BERNARD WILLIS (Read 3 times) Subj: Old Folks BW> Given the trouble in transferring variable values from one sub BW> procedure to another I find that the odd GOSUB within a program BW> still has a place. BW> A label on the line prior to an input statement, which in turn is BW> followed by a simple trap containing a 'GOTO label' if the input BW> condition is not met, can be very useful. The program repeats the BW> input request until the conditional statement requirements have BW> been met. No spaghetti involved. Heck, if you need to transfer a variable value to several procedures, COMMON SHARED is very useful. I use DO: LOOP for that. Let's face it: DO | Again: k$ = INKEY$ | k$ = INKEY$ LOOP UNTIL LEN(k$) | IF LEN(k$) = 0 THEN GOTO Again do exactly the same thing. If they get long and involved, the DO: LOOP is easier to read. Of course, the GOTO _could_ be indented, too. I compared programming to writing letters and I believe that applies here, also: different people have different styles. The above are two styles that yield the same result. That last line could also read: IF NOT LEN(k$) THEN GOTO Again Is one "more correct" than the other? The anti-GOTO purists may think so, but the computer isn't going to care! My main objection with GOTO is that you then have to hunt for the target. GOSUB is worse: you also have to find the source. SUBs and FUNCTIONs can be found with F2 and you return to the CALL location when you F2 back to the calling procedure. Unless you are trying to find it on a print-out! FIDO: Bill White @ 1:135/110 (Miami) InterNet: bill.white@110.sunshine.com * SLMR 2.1a * Great minds are programmed alike! --- Maximus 2.01wb * Origin: Miami Amateur Computer Club BBS/USR Courier V.E (1:135/110) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F4200068 Date: 03/26/98 From: BILL WHITE Time: 02:17pm \/To: BUCKY CARR (Read 3 times) Subj: Old Folks BC> BW> Finally I opened the other side of the panel. On BC> BW> one pin to that module's plug, one wire was wrapped BC> BW> around the terminal WITH THE INSULATION STILL ON IT and BC> BW> not soldered. That wire had never been connected to BC> BW> that pin and in two years of operation no one had BC> BW> called on it to operate. BC> Amazing. Yes, and exactly why I didn't connect it on the spot, just used a jumper. I figured if I peeled off the insulation and soldered the wire, NO ONE would ever believe it, even tho I had the mathematician as a witness. When the day crew arrived, I showed it to the maintenance chief, who immediately called the head mathematician. We ended with quite a crowd shaking their heads. And worrying about what undetected errors this might have caused. No further "work" was done for a couple of days while tests were made, proving that any attempt to use this wire unconnected would result in a machine failure and not a mathematical error. Big sigh of relief! FIDO: Bill White @ 1:135/110 (Miami) InterNet: bill.white@110.sunshine.com * SLMR 2.1a * Pandora's Law: Never open a box you didn't close yourself --- Maximus 2.01wb * Origin: Miami Amateur Computer Club BBS/USR Courier V.E (1:135/110) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F4200069 Date: 03/29/98 From: BILL WHITE Time: 12:37am \/To: BRUCE CORBETT (Read 3 times) Subj: Old Folks BC> Any ideas where I could get a copy of this? or if its a public domain file BC> could you post it? It sounds quite intresting..... and is somthing that I BC> need for some of thoose bigger programs that I make. Not PD. From the InterNet: -------------------------8<------------------------ DON MALIN'S XREF Don Malin's XREF is a sophisticated cross-reference utility for fully documenting an entire application. It lists all variables, arrays, constants and procedures alphabetically by type and scope, even across separate modules. A unique call-tree report identifies procedures showing who calls what, which routines are present but never accessed and more. Main Category / Subcategory:Computers / Resource Optimization Facilities Operating System:MS-DOSLanguage:EnglishList price:$59.00; Site License Plans Are AvailableSW-ID:5678 Software developed by Crescent Software 11 Bailey Avenue Ridgefield, CT 06877 USA Phone: +1 (203) 438-5300 or +1 (800) 352-2742 Fax: +1 (203) 431-4626 New software Search. Back to Software List. TurboGuide Home Page - The cdroms and software directory. Select - Don Malin's XREF -. - DON MALIN'S XREF - -------------------------8<------------------------ I don't use XREF often, but it's really great when I do need it! FIDO: Bill White @ 1:135/110 (Miami) InterNet: bill.white@110.sunshine.com * SLMR 2.1a * Hell is being locked forever in a room with your friends! --- Maximus 2.01wb * Origin: Miami Amateur Computer Club BBS/USR Courier V.E (1:135/110) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F4200070 Date: 03/29/98 From: BILL WHITE Time: 12:39am \/To: PAT PRIDGEN (Read 3 times) Subj: Old Folks PP> Where might the rest of this source code be found Bill? I took a See previous answer to Bruce Corbett. FIDO: Bill White @ 1:135/110 (Miami) InterNet: bill.white@110.sunshine.com * SLMR 2.1a * A closed mouth gathers no feet! --- Maximus 2.01wb * Origin: Miami Amateur Computer Club BBS/USR Courier V.E (1:135/110) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F4200071 Date: 03/29/98 From: BILL WHITE Time: 12:00am \/To: DAVID ROTHSCHILD (Read 3 times) Subj: Multiple eofs DR> How do I read/write files with multiple EOF's (like ZIPs or EXEs)? DR> I'm writing an Encryption program, but it stops at the first EOF. I DR> tried a FOR X = 1 to LOF..... but then I ran into an "Input past end DR> of file", even when there was more file past the EOF. My method is to treat it as a RANDOM file. FIDO: Bill White @ 1:135/110 (Miami) InterNet: bill.white@110.sunshine.com * SLMR 2.1a * SYSOP (sihs-ahp) n.: The person laughing at your typing! --- Maximus 2.01wb * Origin: Miami Amateur Computer Club BBS/USR Courier V.E (1:135/110) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F4200072 Date: 04/01/98 From: BOB LOTSPEICH Time: 11:26am \/To: KEVIN FROST (Read 3 times) Subj: bsave/bload | Quoting from a message by Kevin Frost | To Bob Lotspeich | About - bsave/bload KF> I know how to save ansi graphics, i mean as in pictures you make on KF> the screen using the ling statement or circle or pset. Sorry -- you didn't specify which type of graphics you wanted to BLoad. I'm confused now: if you are creating the graphics with your code, why would you need to BSave and BLoad them? I guess you could compile the graphics as separate .OBJs, then include them in a library, and call them from the library... --- Blue Wave/386 v2.30 * Origin: The Circle Circus * Dale City, VA * 703-730-3115 (1:265/124) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F4200073 Date: 04/02/98 From: BERNARD WILLIS Time: 10:34am \/To: BILL WHITE (Read 3 times) Subj: Old Folks Greetings and thank you for your reply, which is appreciated. BW> Heck, if you need to transfer a variable value to BW>several procedures, COMMON SHARED is very useful. A method which I do use from time to time. Gets a bit complicated when several variables are involved and not necessarily needed on other than a temporary basis. BW> I use DO: LOOP for that. Let's face it: BW>DO | Again: BW> k$ = INKEY$ | k$ = INKEY$ BW>LOOP UNTIL LEN(k$) | IF LEN(k$) = 0 THEN GOTO Again | Again: | Input; "Enter value for X "; VarX | If VarX <= 0 then | Print "Must be greater than zero." | GOTO Again | End if BW>Is one "more correct" than the other? The anti-GOTO BW>purists may think so, but the computer isn't going to BW>care! BW> My main objection with GOTO is that you then have BW>to hunt for the target. GOSUB is worse: you also have to BW>find the source. SUBs and FUNCTIONs can be found with BW>F2 and you return to the CALL location when you F2 back BW>to the calling procedure. Unless you are trying to BW>find it on a print-out! For any permanent program I make a print-out and carefully check for redundant code etc. To help follow the flow I write the label name on the right hand side opposite the actual label and highlight it. For many years I have used highlighter pens to color code such things as Rem entries (Yellow), Gosub and Call (Blue); Goto, Return and End (Red), Message Strings (Green), Variables (Orange) and so on. I find that this method when applied not only to programming print-outs but to examples printed in handbooks and textbooks often makes the operation of a program much easier to follow. Nested loops, including the For ... Next variety, I bracket with neat green lines arrowed to indicate direction. As you say, each individual will probably develop his or her own style. Kia ora Koe, na Bernard. ___ X SLMR 2.0 X Talk is the food of chiefs - Maori proverb. --- Maximus/2 3.01 * Origin: === NZMC Maxie BBS. Ak, NZ +64 9 444-0989 === (3:772/1)