> Is it really 'that bad' to run in interpreted mode?
Running interpreted is not necessarily the problem; although keep in minder
that the end goal for every developer should be a compiled application -
interpreted is for development, not deployment.
> Consequently, Typing Generation and Syntax Checking both fail (since this
> application had never been written with compilation as a goal)
The errors reported by the syntax checker are definitely a problem! They must
be fixed.
The tech tip I linked specifically mentions:
{
If after fixing your code you do not want to run your application compiled,
simply click on the "Clear Compiled Code" button to remove the compiled code.
}
The goal of the tech tip is not to run compiled, but it is to use the
applications built-in tools to check your work for errors. If the built-in
tools are telling you that your code has errors, then well, you have errors
that need to be fixed. The good news is that the compiler makes it super
simple. Usually, you can just double click on the error and it brings you
directly to the line that the problem is referring to (this is described in the
tech tip I linked). Your work is literally cut out for you, just double click
and then fix.
Here is the tip again:
Tech Tip: Using the compiler to check for coding mistakes
http://kb.4d.com/assetid=50223
Kind Regards,
Tim PENNER
From: Noah <[email protected]>
Sent: Wednesday, August 01, 2018 7:34 AM
To: [email protected]
Cc: Timothy Penner <[email protected]>
Subject: Re: Changes to variable initialization in v16?
Thank you both for the speedy replies!
Unfortunately this inherited application IS running in interpreted mode and has
hundreds of errors that would keep it from compiling.
As time permits we will occasionally revisit the compilation errors and work
towards a compiled version (but we have not made it there yet).
Consequently, Typing Generation and Syntax Checking both fail (since this
application had never been written with compilation as a goal)
Do you have any other suggestions?
Is is really 'that bad' to run in interpreted mode?
My original question was simply about the scoping of variable initialization
and form events in version 16.
On Tue, Jul 31, 2018 at 3:25 PM Timothy Penner via 4D_Tech
<[email protected]<mailto:[email protected]>> wrote:
In addition to what has already been said -
Using a compilation path of "All variables are typed" is highly recommended:
http://kb.4d.com/assetid=50223
-Tim
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:
mailto:[email protected]<mailto:[email protected]>
**********************************************************************
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
