--------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F3P00006 Date: 03/19/98 From: BUCKY CARR Time: 02:08pm \/To: CHRIS GUNN (Read 2 times) Subj: Old Folks CG> I gather MicroSoft is hiring programmers that don't have the skills to CG> organize their code these days. So they end up with dozens of CG> subroutines that perform the same kind of things, which if organized, CG> one subroutine would handle. The amount of compiled code sure CG> indicates some sloppy design work. I think the trap they are falling into is the same one that is luring me into sloppiness - almost limitless memory. I find that to get a working version going I would rather change a bit of code slightly and make it a new Sub/Function than to figure a clever way of using existing code to do the same thing. Bloats the code terribly for now. Goal of course is to go back and make it look better/smaller later. We all know how that works. --- PPoint 2.00 * Origin: Vanishing Point (1:15/7.1) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F3P00007 Date: 03/19/98 From: BUCKY CARR Time: 02:11pm \/To: RICK PEDLEY (Read 2 times) Subj: Old Folks BC> Are you confessing to documenting your code? You can be banished from BC> this echo forever if anyone finds out you do that. RP> I'll sometimes REM out lines of code that didn't work and leave them RP> there so I won't make the same stupid mistake next time - does that RP> count? :) haha. I do that too, but usually only on the 3rd or 4th try at the same stupid mistakes. --- PPoint 2.00 * Origin: Vanishing Point (1:15/7.1) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F3P00008 Date: 03/18/98 From: RICHARD GRIFFITHS Time: 10:59pm \/To: ALL (Read 2 times) Subj: PKT Files Hi All, Can someone tell me how to read/write to a PKT (netmail) file? I'm writing my own message writer, and I desperately need the code to do this. Any help ould be gratefully received. Thanks, --------------------------------------------------------------------------- Regards, FidoNet : 2:254/292.3 Richard Griffiths Email : Rich@TheArc.CrayBBS.co.uk CoSysop of Burp's BBS UK Burp's BBS: ++44 (0)181 405 4164 --------------------------------------------------------------------------- .!. Whip me, beat me, make me use an offline storage reader. --- The Ripped One * Origin: The Co-Sysop of Burp's BBS UK: ++44(0)181 405 4164 (2:254/292.3) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F3R00000 Date: 03/21/98 From: KURT KUZBA Time: 01:30am \/To: PAUL ROBINSON (Read 3 times) Subj: ports HEX address PR> in an example in qbasic, i saw this PR> &H3FC PR> which stands for com 1 PR> but i cant find the address for ports 1-4 PR> it was used in the example.... PR> INP(&H3FC) PR> with OUT etc This code is actually untested, since I never had a need to use it. I suppose I should test it, really, just to see if it actually works. [ ... ] Well.. It works, but I still can't get it to do 115200 bps. Oh well... There must be something else involved I'm not taking into account. Anyway, here it is. The addresses for comm 1-4 are included in it. '_|_|_| SETBPS.BAS '_|_|_| Untested subroutine to set BPS rate on an open COM. '_|_|_| No guarantee or warrantee is given or implied. '_|_|_| Released PUBLIC DOMAIN by Kurt Kuzba. (12/12/96) DECLARE SUB SetBPS (port%, bps&) DIM COMM(1 TO 4) AS INTEGER COMM(1) = &H3F8: COMM(2) = &H2F8: COMM(3) = &H3E8: COMM(4) = &H2E8 ' open com before setting bps rate. ' example SetBPS COMM(2), 19200 ' based on data contained in a book published by QUE ' Using Assembly Language by Allen L. Wyatt '_|_|_| end SETPBS.BAS SUB SetBPS (port%, bps&) ' Valid BPS rates: ' 115200, 19200, 9600, 4800, 2400, 1200, 300, 110 Div& = 115200 \ bps&: hi% = Div& \ 256: lo% = Div& AND 255 OUT port% + 3, INP(port% + 3) OR 128 OUT port%, lo%: OUT port% + 1, hi% OUT port% + 3, INP(port% + 3) XOR 128 END SUB > ] I'm heavily sedated and seriously thinking about blinking... --- * Origin: *YOPS ]I[* 8.4 GIG * RA/FD/FE * Milwaukee, WI (1:154/750) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F3R00001 Date: 03/20/98 From: NICK ANDRE Time: 06:05am \/To: ALL (Read 3 times) Subj: Test TEst --- Renegade v5-11 Exp * Origin: Andre Computers OS/2 (705)445-8609 (1:252/0) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F3R00002 Date: 03/21/98 From: DAVID WILLIAMS Time: 09:42am \/To: BUCKY CARR (Read 3 times) Subj: Old Folks -> I think the trap they are falling into is the same one that is luring -> me into sloppiness - almost limitless memory. I find that to get a -> working version going I would rather change a bit of code slightly -> and make it a new Sub/Function than to figure a clever way of using -> existing code to do the same thing. Bloats the code terribly for -> now. I have seen many programs that include large chunks of code that are never executed under any circumstances. The programmer had second thoughts, and never bothered to clean up after himself. I have sometimes wondered if it might be possible to do this automatically - to set up some sort of "supervisor" which would watch a program as it is running for a long time, and take note of any bits that are never used. Eventually, it would cut them out. But, of course, this would probably cause problems by removing error traps and the like, which are executed only very rarely but are very valuable when they are needed. dow --- PCBoard (R) v15.3 (OS/2) 5 * Origin: FidoNet: CAP/CANADA Support BBS : 416 287-0234 (1:250/710) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F3R00003 Date: 03/20/98 From: TERRY MUELLER Time: 09:46am \/To: DAVID AUKERMAN (Read 3 times) Subj: Re: Code FAQ 03/98 01/12 David, Could you please indentify on the 1st page whether there are any changes from the previous release? I generally copy all of the messages to disk just to be sure I haven't missed something new. I would like to do that only if there has been a change to the FAQ. Thanks, Terry --- Sirius 1.0ya * Origin: Boeing Employees Rec. Computer Club (314-830-4287) (1:100/10) --------------- FIDO MESSAGE AREA==> TOPIC: 125 QUICK BASIC Ref: F3R00004 Date: 03/21/98 From: HARRY HICKEY Time: 12:46am \/To: ALL (Read 3 times) Subj: Documenting Code This is verging towards off-topic, but since lots of folks on this echo are interested in the matter of code that is documented (vs the other kind): WHEREAS: The great multitude of Programmers consider Documentation a wearisome and irksome Exercise; and WHEREAS: In consequence whereof, a great deal of Source Code goes forth with little or no Documentation, to the great detriment of those who would seek to make intelligent use of the aforesaid Code; and WHEREAS: The labor supply of qualified Journalists is equal to or perhaps in excess of demand for their services; and WHEREAS: The reverse is true with respect to qualified Programmers; and WHEREAS: The professional training of Journalists is in the skills of explaining new matters to the Public in a clear, concise, and readable manner; NOW THEREFORE BE IT RESOLVED: That Efforts be undertaken by Software producers to recruit and cross-train qualified Journalists as Programmers, to the end that the imbalance in labor supply be redressed, and the World will be supplied with Programmers who are habituated to producing Code with appropriate Documentation. -!- SLMR 2.1a Galactic Dept of Wts & Measures: TAKE US TO YOUR LITER! --- * Origin: * My Place BBS * 28.8 V.34 * Bowie, Md * (301)805-1602 * (1:109/570)