Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 2 of 2 total
Thread Compile Errors
Tue, Mar 3 2020 11:20 PMPermanent Link

Richard Harding

Wise Nutrition Coaching

Tim,

There is a closing bracket missing on line 1537 {$ENDIF of WebData.wbs which messes up the formatting in Notepad++.

I have 3 compile errors in an existing project.

Random does not seem to be defined in EWB3.

I have a compile error in GridColumn.OnCellUpdate.
Assigned(ACell.Data) results in
[Error] Menu.wbs (383,7): Cannot find a function, procedure, or method declaration that matches the Assigned reference.

I cannot compile the new Dataset.Find.
     if not Find(['Category', 'Number'], [fActiveCategory, fActiveNumber], false, true, true) then

[Error] Menu.wbs (449,61): Invalid expression type found, expected string, character, or variant

Any clues are appreciated.

Richard
Wed, Mar 4 2020 2:25 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Richard,

<< There is a closing bracket missing on line 1537 {$ENDIF of WebData.wbs which messes up the formatting in Notepad++. >>

Got it, thanks.  I fixed the problem in the source, but the compiler isn't catching unterminated strings, comments, or directives, and needs to be.  It's just a quirk of how the tokenizing now works in the source manager.

<< Random does not seem to be defined in EWB3. >>

This is fixed for build 3.

<< I have a compile error in GridColumn.OnCellUpdate.
Assigned(ACell.Data) results in
[Error] Menu.wbs (383,7): Cannot find a function, procedure, or method declaration that matches the Assigned reference. >>

Yes, this is another change that I forgot to log.  You can now only use Assigned with references that can be nil.  Strings are no longer supported because the EWB 3 compiler never allows nil strings.  Therefore, just remove the Assigned check in that instance and you'll be fine.

<< I cannot compile the new Dataset.Find.
     if not Find(['Category', 'Number'], [fActiveCategory, fActiveNumber], false, true, true) then >>

This is fixed for build 3.  The problem here was the compiler getting overly-aggressive with type-checking constant arrays in situations where the target array element type was a Variant.

Thanks !

Tim Young
Elevate Software
www.elevatesoft.com
Image