Not to mention the infidel CLEAR statement that does the same thing, hides
errors.
I believe the practice of variable assignment at the top is a practice
brought over from other languages where all variables apparently need to be
defined up front with DIM statements and variable types. I support s
:-)).
Regards
David
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Bill H.
Sent: Thursday, March 04, 2004 5:41 AM
To: U2 Users Discussion List
Subject: RE: [UV] Variable never assigned a value warning
Marco:
A useful alternative, which noone has ever
o a soapbox. It's a sore spot where I keep
getting poked.
cds
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Marco Manyevere
> Sent: Wednesday, March 03, 2004 8:18 PM
> To: U2 Users Discussion List
> Subject: RE: [UV] Variable n
My query is not on how to suppress the warning messages but on why the compiler
catches only a few of them. Even the case statement example you gave is in my opinion
a good candidate for such warning messages because a robust program would have to
provide for a default case block, something lik
> The easy answer is no. This would require the compiler to establish all
> possible paths through a program and determine whether it was possible to
> arrive at any place that uses a variable without setting it
> first. Although
> some compilers (many C compilers for example) make a good attempt
> Is it technically or theoretically possible for the BASIC
> compiler (or any other compiler for that matter) to catch
> (during compilation) all the situations that might result in
> the use of unassigned variable at runtime within the scope of
> the subroutine being compiled?
It's not exact
numeric required; zero used.
Stupid questions for the exasperated business developer?
Bill
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Martin Phillips
> Sent: Wednesday, March 03, 2004 12:42 AM
> To: U2 Users Discussion List
> Subject: R
HEAR, HEAR!
> Incidentally, I find the worryingly common practice of
> setting all variables to zero / null at the top of a program
> very annoying as it hides the very useful unassigned variable
> trap, leaving you thinking your program works when actually
> it doesn't.
>
> Martin Phillips
>
Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Marco Manyevere
Sent: 03 March 2004 06:32
To: [EMAIL PROTECTED]
Subject: [UV] Variable never assigned a value warning
Hi All,
Is it technically or theoretically possible for the BASIC
compiler (or any oth
PROTECTED] On Behalf Of Marco Manyevere
> Sent: 03 March 2004 06:32
> To: [EMAIL PROTECTED]
> Subject: [UV] Variable never assigned a value warning
>
> Hi All,
>
> Is it technically or theoretically possible for the BASIC
> compiler (or any other compiler for that matter
ptional. I wouldn't like to try to support their code!
Martin Phillips
Ladybridge Systems
17b Coldstream Lane, Hardingstone, Northampton NN4 6DB
+44-(0)1604-709200
- Original Message -
From: "Marco Manyevere" <[EMAIL PROTECTED]>
Subject: [UV] Variable never assig
Hi All,
Is it technically or theoretically possible for the BASIC compiler (or any other
compiler for that matter) to catch (during compilation) all the situations that might
result in the use of unassigned variable at runtime within the scope of the subroutine
being compiled? Under what circu
12 matches
Mail list logo
