Some other options are "null" or "nil".

Mike



On 1/5/2019 4:53 AM, ingo wrote:
> A feature request,
> 
> #declare Arr = array[10]{};
> #declare Arr[3]= 5;
> this results in a partially 'filled' array that can't be written to a
> file and then #included.
> Something like #declare Arr = array[10]{,,,5,,,,..} won't work.
> 
> True, false & co. are values, so I can't put those as fillers in an array
> with values as they will be seen as legit values. They can't be used in
> an array with strings or objects (unless the array is of mixed type).
> 
> In an array with strings one could use an empty string "", in an array
> with values an odd one, -9999.99, same with vectors.
> You can't use an empty object{} anywhere.
> 
> Could a 'none' keyword be introduced as a general placeholder for
> emptyness?
> object{none}
> #declare Arr = array[10]{none,none,none,5,...}
> #if(... none)
> #while(... none)
> #ifndef(Arr[I])#write(File,none)#end
> #macro DoThing(A, optional B, optional C)
> DoThing("Great thing", none, true)
> 
> ingo
>

Post a reply to this message