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 (1) with a space in their names On Mon, 19 Aug 2019 11:12:57 -0500, John DeSoi via 4D_Tech wrote: > 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 >> <[email protected]> wrote: >> >> This causes the 'module headers' to float to the top of the module >> method list. >> ex: >> animal Module_Info >> animal_a >> animal_b >> .... >> >> Again, 64 bit 4D is not going to like this. Ideas to solve this, or do >> I just forego the ' module headers'? > > ********************************************************************** > 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] > ********************************************************************** --------------- Gas is for washing parts Alcohol is for drinkin' Nitromethane is for racing ********************************************************************** 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] **********************************************************************
