Conditional Array Definitions

[John Esak]

It's amazing, but my initial investigations show that 9.0 AOL can NOT send
text messages.  Sheesh, what a design decision that is.

Good luck,

John

  -----Original Message-----
  From: filepro-list-bounces at lists.celestial.com
[mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of
Transpower at aol.com
  Sent: Saturday, November 27, 2004 6:39 PM
  To: kenbrody at bestweb.net
  Cc: filepro-list at seaslug.org
  Subject: Re: Conditional Array Definitions


  In a message dated 11/27/2004 6:18:29 PM Eastern Standard Time,
kenbrody at bestweb.net writes:


    I didn't see the message to which John is replying, but...

    I see nothing "counter-intuitive" about declarations being just that.
    They declare the variable.  They do not generate any code.  They do not
    need to be executed.

    And, excluding Visual BASIC's "DIM" command, nothing else comes to mind
    as an example of "most other computer languages" where you must actually
    execute a variable declaration.  (Not that I've thought about it very
    hard, mind you.)




  Ken:

  Well, filePro processing was roughly based on Basic...
  In TrueBASIC, one uses a DIM statement at the beginning, usually setting
an array to  minimal dimensions (i.e., 1); then, in the body of the code, a
MAT REDIM statement is inserted to resize the array to fit the current
running problem.  This is probably what the original poster had in mind.

  I've checked through some of my existing filePro commercial code and
cannot find any place where I've conditionally DIM'd an array by itself.  I
did find one place where I did that along with setting other variables on
the same line.  No harm, no foul, I guess.  There is no syntax error or
warning message if one defines an array with an If statement.  Something
like: "Note:  the array will be defined whether the condition is true or
not."  The only downside is an increase in memory, which given the
tremendous amount of RAM in existing computers, is not a problem...at lease
most of the time.

  As far as HTML mail, I'm using whatever AOL 8.0 mails; my AOL 9.0 program
crashed a long time ago--some C language DLL seems to be corrupted and
uninstalling and reinstalling doesn't correct the problem.  If I could
configure AOL 8.0 to send out plain text I certainly would.

  Regards,
  RWS
  transpower at aol.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.celestial.com/pipermail/filepro-list/attachments/20041127/50fb81f5/attachment.html