Xref: utzoo alt.religion.computers:2544 comp.windows.ms.programmer:3249 Path: utzoo!utgpu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!hobbes.physics.uiowa.edu!maverick.ksu.ksu.edu!matt.ksu.ksu.edu!rogerhef From: rogerhef@matt.ksu.ksu.edu (Roger Heflin) Newsgroups: alt.religion.computers,comp.windows.ms.programmer Subject: Re: ap, Windows BASIC Message-ID: <1991Jun22.040758.9453@maverick.ksu.ksu.edu> Date: 22 Jun 91 04:07:58 GMT References: <1991Jun20.034205.2661@maverick.ksu.ksu.edu> <7451@vela.acs.oakland.edu> Sender: news@maverick.ksu.ksu.edu (The News Guru) Organization: Kansas State University Lines: 18 Nntp-Posting-Host: matt.ksu.ksu.edu In <7451@vela.acs.oakland.edu> awesley@vela.acs.oakland.edu (WESLEY ANTHONY ) writes: >This is great stuff! Is this going to rec.humor.funny? How do I >force QBasic to flag an undeclared variable as an error. If I mistype >a long variable, no error message, just a new variable. Didn't everyone >figure out this was a Bad Feature (TM) in a programming language way >back around FORTRAN-66 or so? Can you find me a language that will warn you if you mistype a variable? Without using something like lint. C assumes you knew what you were doing. Is QB wrong for making that assumption, at least QB doesn't let you mix your strings and numeric variables up. By default C has that Bad Feature that you mentioned. -- Rogerhef@Matt.ksu.ksu.edu Roger Heflin EECE Grad Student (913) 532-5600