On 6/21/19 11:49 AM, Ilias Stamatis wrote:
>
I totally agree with you, it's more readable for me too.
Just so far I haven't encountered in the code. Also e.g. C99 allows
variables to be declared inside a loop ie
for (size_t i = 0; ...
...but I haven't seen that being used anywhere either.
On Fri, Jun 21, 2019 at 10:03 AM Michal Privoznik wrote:
>
> On 6/20/19 7:36 PM, Ilias Stamatis wrote:
> > On Thu, Jun 20, 2019 at 5:57 PM Michal Privoznik
> > wrote:
> >>
> >> On 6/19/19 6:45 PM, Ilias Stamatis wrote:
> >>> testDomainInterfaceAddresses always returns the same hard-coded
> >>> a
On 6/20/19 7:36 PM, Ilias Stamatis wrote:
On Thu, Jun 20, 2019 at 5:57 PM Michal Privoznik wrote:
On 6/19/19 6:45 PM, Ilias Stamatis wrote:
testDomainInterfaceAddresses always returns the same hard-coded
addresses. Change the behavior such as if there is a DHCP range defined,
addresses are re
On Thu, Jun 20, 2019 at 5:57 PM Michal Privoznik wrote:
>
> On 6/19/19 6:45 PM, Ilias Stamatis wrote:
> > testDomainInterfaceAddresses always returns the same hard-coded
> > addresses. Change the behavior such as if there is a DHCP range defined,
> > addresses are returned from that pool.
> >
> >
On 6/19/19 6:45 PM, Ilias Stamatis wrote:
testDomainInterfaceAddresses always returns the same hard-coded
addresses. Change the behavior such as if there is a DHCP range defined,
addresses are returned from that pool.
The specific address returned depends on both the domain id and the
specific g
testDomainInterfaceAddresses always returns the same hard-coded
addresses. Change the behavior such as if there is a DHCP range defined,
addresses are returned from that pool.
The specific address returned depends on both the domain id and the
specific guest interface in an attempt to return uniqu
