> I just posted it in the forums. I agree there are other things that are
> probably more important but this seems like something that could be set as
> an option pretty easily.
And perhaps if they decide to do a set of compiler changes, they'll find
it's easy to do several all in one go. Who
Kirk,
How many times have you heard that from one (or more) of your users??
"Kirk, ole buddy, ole pal..
You know.. I think that if you just.. this
program would be GREAT!, er um.. maybe Yuge!"
:)
On Fri, 28 Apr 2017 08:11:18 -0700, Kirk Brooks via 4D_Tech wrote:
> David,
>
> I just posted
David,
I just posted it in the forums. I agree there are other things that are
probably more important but this seems like something that could be set as
an option pretty easily.
Topic : *Compiler - don't duplicate declarations*
http://forums.4d.fr/Post//19356198/1/
On Thu, Apr 27, 2017 at
If you compile with all variables typed and do not generate typing you will get
a list of errors and can fix. Certainly it becomes a habit ingrained over time
Regards
Chuck
Chuck Miller Voice: (617)
> What I wish is I could tell Compiler "when you look to see if a variable
is
> declared consider it done if you find it in any method name 'Compiler_@'."
> I won't replicate my declarations but will find anything I miss.
Why not post this to the feature request forums and see if you get some
Maybe I am missing something -
Is there an actual issue you are seeing with the declarations being listed both
in your compiler methods and also in 4D's official compiler methods?
I mean, is there a performance hit, or an error that you are encountering?
-Tim
Chuck,
On Thu, Apr 27, 2017 at 2:29 PM, Charles Miller via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> It never worked that way. I agree this would be a good thing but I always
> want to type variables so never run your option
>
I want to type the variables too. But I'm not perfect. And I've seen
On Thu, Apr 27, 2017 at 2:49 PM, Kirk Brooks via 4D_Tech <
4d_tech@lists.4d.com> wrote:
>
> I think it used to work that way a few versions ago but I may be wrong. To
> me it would make these sort of 'custom' declaration methods more useful.
It never worked that way. I agree this would be a
Hey Tim,
On Thu, Apr 27, 2017 at 10:43 AM, Timothy Penner via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> So my understanding is, if you have written your own methods that begin
> with compiler_ that are not specifically defined in the Database Settings
> then use the Generate Typing button; then
Hi Kirk,
In the Database Settings, at the bottom of the Compiler tab, there is a section
of "Compiler methods for..."
This section lets you define the names of the 5 compiler methods that 4D use
for type declarations.
http://livedoc.4d.com/4Dv16/help/Title/en/page1261.html#460189
My
I prefer to run the compiler with the "all variables are typed" option. I
also run the "Generate Typing" command before compiling. IN a lot fo
projects I don't bother to separate out the typing commands from the ones
4D generates because it's just not important to me but that's another
thread.
On
11 matches
Mail list logo