 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'm trying to write a script that gets its objects from arrays. However,
some of these arrays are empty, and cause parsing to stop. Why are zero
length arrays not allowed? This is not true of most of the programming
languages I am familiar with, and means I have to write a lot of extra
code to handle this situation.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 05.02.2016 um 02:56 schrieb Mike Horvath:
> I'm trying to write a script that gets its objects from arrays. However,
> some of these arrays are empty, and cause parsing to stop. Why are zero
> length arrays not allowed?
Because.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I'm trying to write a script that gets its objects from arrays. However,
> some of these arrays are empty, and cause parsing to stop. Why are zero
> length arrays not allowed? This is not true of most of the programming
> languages I am familiar with, and means I have to write a lot of extra
> code to handle this situation.
In C# (which I mostly use) if there is any chance there will be zero
elements then I normally use a List rather than an array. I believe
there is something similar in C++, and probably in other languages too.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/4/2016 8:56 PM, Mike Horvath wrote:
> I'm trying to write a script that gets its objects from arrays. However,
> some of these arrays are empty, and cause parsing to stop. Why are zero
> length arrays not allowed? This is not true of most of the programming
> languages I am familiar with, and means I have to write a lot of extra
> code to handle this situation.
>
If I have an array that may be of size 0, then I just don't define it
and later check for #ifdef when I want to use it.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/5/2016 4:16 AM, dick balaska wrote:
> On 2/4/2016 8:56 PM, Mike Horvath wrote:
>> I'm trying to write a script that gets its objects from arrays. However,
>> some of these arrays are empty, and cause parsing to stop. Why are zero
>> length arrays not allowed? This is not true of most of the programming
>> languages I am familiar with, and means I have to write a lot of extra
>> code to handle this situation.
>>
>
> If I have an array that may be of size 0, then I just don't define it
> and later check for #ifdef when I want to use it.
>
This means I will have to rewrite Chris Colefax's CityGen, since he uses
arrays to store lots of stuff. :(
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 05.02.2016 8:43, scott wrote:
> In C# (which I mostly use) if there is any chance there will be zero
> elements then I normally use a List rather than an array.
Why? This seems perfectly legal in C#:
double[] x = new double[0];
Console.WriteLine(x.Length); // 0
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 6-2-2016 1:01, Mike Horvath wrote:
> On 2/5/2016 4:16 AM, dick balaska wrote:
>> On 2/4/2016 8:56 PM, Mike Horvath wrote:
>>> I'm trying to write a script that gets its objects from arrays. However,
>>> some of these arrays are empty, and cause parsing to stop. Why are zero
>>> length arrays not allowed? This is not true of most of the programming
>>> languages I am familiar with, and means I have to write a lot of extra
>>> code to handle this situation.
>>>
>>
>> If I have an array that may be of size 0, then I just don't define it
>> and later check for #ifdef when I want to use it.
>>
>
> This means I will have to rewrite Chris Colefax's CityGen, since he uses
> arrays to store lots of stuff. :(
Then why does CityGen work in its original state? Or so I remember from
the past...
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
