Re: _ as first character in Method Name [was 64 bit...]

2019-08-24 Thread Keisuke Miyako via 4D_Tech
Hello rhe extended 255 lengrh applies to form object names. ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub:

Re: _ as first character in Method Name [was 64 bit...]

2019-08-24 Thread Narinder Chandi via 4D_Tech
Date: Saturday, 24 August 2019 at 17:39 To: 4D Tech Mailing List <4d_tech@lists.4d.com> Cc: Jim Labos - infobase Subject: Re: _ as first character in Method Name [was 64 bit...] I haven't started to look at v17. Are we still limited to 32 characters for M

Re: _ as first character in Method Name [was 64 bit...]

2019-08-24 Thread Jim Labos - infobase via 4D_Tech
I haven't started to look at v17. Are we still limited to 32 characters for Method and Variable names? - Jim Labos - infobase -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ** 4D Internet Users Group

Re: _ as first character in Method Name [was 64 bit...]

2019-08-20 Thread Peter Bozek via 4D_Tech
On Mon, Aug 19, 2019 at 9:58 PM Keisuke Miyako via 4D_Tech < 4d_tech@lists.4d.com> wrote: > 4D already uses some private property names, > > e.g. > > __LockerID > __NEW > __KEY > > > https://doc.4d.com/4Dv17R5/4D/17-R5/dataClassfromCollection.305-4128671.en.html > >

Re: _ as first character in Method Name [was 64 bit...]

2019-08-19 Thread Keisuke Miyako via 4D_Tech
4D already uses some private property names, e.g. __LockerID __NEW __KEY https://doc.4d.com/4Dv17R5/4D/17-R5/dataClassfromCollection.305-4128671.en.html https://doc.4d.com/4Dv17R5/4D/17-R5/Shared-objects-and-shared-collections.300-4128430.en.html so beware. > 2019/08/20 2:12、Chip Scheide via

Re: _ as first character in Method Name [was 64 bit...]

2019-08-19 Thread Chip Scheide via 4D_Tech
On Mon, 19 Aug 2019 09:31:09 -0700, Tom Benedict wrote: > How about two underscores instead of a space? DUH of course that will work! Chip > > Tom > >> On Aug 19, 2019, at 08:38, Chip Scheide via 4D_Tech >> <4d_tech@lists.4d.com> wrote: >> >> related... >> >> I name project methods in

Re: _ as first character in Method Name [was 64 bit...]

2019-08-19 Thread Chip Scheide via 4D_Tech
On Mon, 19 Aug 2019 17:37:19 +0100, Narinder Chandi via 4D_Tech wrote: > > Personally, I've never used spaces (or all uppercase for that matter) > when naming any 4D object but spaces are allowable and actually > encouraged according to that above?! I only use a space in the specific instance

Re: _ as first character in Method Name [was 64 bit...]

2019-08-19 Thread Narinder Chandi via 4D_Tech
>> and 4D then processes to list all method names, and forms (1) with a space >> in their names ...and actually, by chance I was reading the v17.2 docs at the weekend which explicitly states: "Tip: It is a good programming technique to adopt the same naming convention as the one used by 4D

Re: _ as first character in Method Name [was 64 bit...]

2019-08-19 Thread Tom Benedict via 4D_Tech
How about two underscores instead of a space? Tom > On Aug 19, 2019, at 08:38, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > related... > > I name project methods in 'modules', that is the first 3 - 7 characters > are the same. > i.e. animal_ > I also have a 'header method',

Re: _ as first character in Method Name [was 64 bit...]

2019-08-19 Thread Chip Scheide via 4D_Tech
from my 64 Bit compatibility report: "Naming Conventions If Object Notation is enabled, naming conventions of items must not conflict with the object notation format. Even if Object Notation is not enabled, an MSC verify will complain. " and 4D then processes to list all method names, and forms

Re: _ as first character in Method Name [was 64 bit...]

2019-08-19 Thread Kirk Brooks via 4D_Tech
I agree. I haven't found anything indicating a leading underscore is not allowed. Miyako said it's discouraged to avoid unintended consequences. That's a lot different than not allowed. I'm using, and compiling, leading underscore methods in 17r6 without issues. On Mon, Aug 19, 2019 at 9:13 AM

Re: _ as first character in Method Name [was 64 bit...]

2019-08-19 Thread John DeSoi via 4D_Tech
Why is 64 bit 4D not going to like it? Spaces are still allowed in method names. You could also use animal__Module_Info (2 underscores) to keep it at the top. John DeSoi, Ph.D. > On Aug 19, 2019, at 10:38 AM, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > This causes the

Re: _ as first character in Method Name [was 64 bit...]

2019-08-19 Thread Chip Scheide via 4D_Tech
related... I name project methods in 'modules', that is the first 3 - 7 characters are the same. i.e. animal_ I also have a 'header method', which is all comments and has a summary of the function of the module. I currently name these 'module headers' with the module name + space +

Re: _ as first character in Method Name [was 64 bit...]

2019-08-19 Thread Narinder Chandi via 4D_Tech
of 4D Tech Mailing List <4d_tech@lists.4d.com> Reply-To: 4D Tech Mailing List <4d_tech@lists.4d.com> Date: Monday, 19 August 2019 at 16:27 To: 4D Tech Mailing List <4d_tech@lists.4d.com> Cc: Pat Bensky Subject: Re: _ as first character in Method Name [was 64 bit...] Hi Chip,

Re: _ as first character in Method Name [was 64 bit...]

2019-08-19 Thread Pat Bensky via 4D_Tech
Hi Chip, Yes, we've been doing that for years also ... and sometimes a dot, which also is not allowed any more. We've changed them all to "aa..." Pat On Mon, 19 Aug 2019 at 16:24, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> wrote: > I use an underscore to start the name of methods which I

_ as first character in Method Name [was 64 bit...]

2019-08-19 Thread Chip Scheide via 4D_Tech
I use an underscore to start the name of methods which I want to 'float' to the top of the method list. I.E. _Conventions What allowed character(s) can I use instead? Thanks Chip On Sat, 17 Aug 2019 06:03:27 +, Keisuke Miyako via 4D_Tech wrote: > underscore prefixes are reserved for