I can't agree more. Array was not mentioned in Chip's original post.
Always decide size of array before hand by evaluating the source using position
to count stop char or using \ and % to calculate if length of element is
deciding factor.
Alan Chan
4D iNug Technical <4d_tech@lists.4d.com> writes:
>On Thu, Nov 17, 2016 at 11:43 AM, Arnaud de Montard <arn...@init5.fr> wrote:
>
>> huge text in a text array makes it much easier to manipulate, but, at the
>> end, 4D memory is the same. In my example of 6,6Gb file, it was not a
>> solution.
>
>
>Also it might be creation of array. Remember that every time 4D resizes an
>array especially bigger, it looks for a block of memory that can hold it
>all. In effect copying array over and over
>
>Think of it this way
>
>Array text($Somtext;0)
>insert element($Somtext;size of array(Somtext)+1)
>$Somtext{size of array(Somtext)}:="bkjbkjbkb" `copy one
>
>
>insert element($Somtext;size of array(Somtext)+1)
>$Somtext{size of array(Somtext)}:="bkjbkjbkb" `copy two
>
>etc each looking for larger chunks of continuos memory
>
>Regards
>
>Chuck
>
>
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************
