If that's all they are used for - the native interface to the same
thing, then fine.
But then write that down too in the comments that this is simply that...
geir
Alexey Varlamov wrote:
2006/12/14, Geir Magnusson Jr. <[EMAIL PROTECTED]>:
Alexey Varlamov wrote:
> 2006/12/13, Geir Magnusson
Geir Magnusson Jr. wrote:
Gregory Shimansky wrote:
Tim Ellison wrote:
Gregory Shimansky wrote:
Tim Ellison wrote:
Maybe we do, i.e. where there is no value "-Dfoobar". So perhaps we
need to say that GetSystemProperty returns VMI_ERROR_NONE and sets the
the *valuePtr to NULL if there is no
2006/12/14, Geir Magnusson Jr. <[EMAIL PROTECTED]>:
Alexey Varlamov wrote:
> 2006/12/13, Geir Magnusson Jr. <[EMAIL PROTECTED]>:
>>
>>
>> Gregory Shimansky wrote:
>> > Alexey Varlamov wrote:
>> >> 2006/12/13, Gregory Shimansky <[EMAIL PROTECTED]>:
>> >>> Tim Ellison wrote:
>> >>> > Alexey Varla
Alexey Varlamov wrote:
2006/12/13, Geir Magnusson Jr. <[EMAIL PROTECTED]>:
Gregory Shimansky wrote:
> Alexey Varlamov wrote:
>> 2006/12/13, Gregory Shimansky <[EMAIL PROTECTED]>:
>>> Tim Ellison wrote:
>>> > Alexey Varlamov wrote:
>>> >> Is there any reason to distinguish these cases? I supp
2006/12/13, Geir Magnusson Jr. <[EMAIL PROTECTED]>:
Gregory Shimansky wrote:
> Alexey Varlamov wrote:
>> 2006/12/13, Gregory Shimansky <[EMAIL PROTECTED]>:
>>> Tim Ellison wrote:
>>> > Alexey Varlamov wrote:
>>> >> Is there any reason to distinguish these cases? I suppose no, then
>>> >> return
Gregory Shimansky wrote:
Tim Ellison wrote:
Gregory Shimansky wrote:
Tim Ellison wrote:
Maybe we do, i.e. where there is no value "-Dfoobar". So perhaps we
need to say that GetSystemProperty returns VMI_ERROR_NONE and sets the
the *valuePtr to NULL if there is no value; and returns a
VMI_ER
Gregory Shimansky wrote:
Alexey Varlamov wrote:
2006/12/13, Gregory Shimansky <[EMAIL PROTECTED]>:
Tim Ellison wrote:
> Alexey Varlamov wrote:
>> Is there any reason to distinguish these cases? I suppose no, then
>> returned NULL is fine.
>
> Maybe we do, i.e. where there is no value "-Dfooba
Tim Ellison wrote:
Gregory Shimansky wrote:
Tim Ellison wrote:
Maybe we do, i.e. where there is no value "-Dfoobar". So perhaps we
need to say that GetSystemProperty returns VMI_ERROR_NONE and sets the
the *valuePtr to NULL if there is no value; and returns a
VMI_ERROR_NOT_FOUND if the propert
2006/12/13, Gregory Shimansky <[EMAIL PROTECTED]>:
Alexey Varlamov wrote:
> 2006/12/13, Gregory Shimansky <[EMAIL PROTECTED]>:
>> Tim Ellison wrote:
>> > Alexey Varlamov wrote:
>> >> Is there any reason to distinguish these cases? I suppose no, then
>> >> returned NULL is fine.
>> >
>> > Maybe we
Alexey Varlamov wrote:
2006/12/13, Gregory Shimansky <[EMAIL PROTECTED]>:
Tim Ellison wrote:
> Alexey Varlamov wrote:
>> Is there any reason to distinguish these cases? I suppose no, then
>> returned NULL is fine.
>
> Maybe we do, i.e. where there is no value "-Dfoobar". So perhaps we
> need to
Gregory Shimansky wrote:
> Tim Ellison wrote:
>> Maybe we do, i.e. where there is no value "-Dfoobar". So perhaps we
>> need to say that GetSystemProperty returns VMI_ERROR_NONE and sets the
>> the *valuePtr to NULL if there is no value; and returns a
>> VMI_ERROR_NOT_FOUND if the property is unde
2006/12/13, Gregory Shimansky <[EMAIL PROTECTED]>:
Tim Ellison wrote:
> Alexey Varlamov wrote:
>> Is there any reason to distinguish these cases? I suppose no, then
>> returned NULL is fine.
>
> Maybe we do, i.e. where there is no value "-Dfoobar". So perhaps we
> need to say that GetSystemPrope
Tim Ellison wrote:
Alexey Varlamov wrote:
Is there any reason to distinguish these cases? I suppose no, then
returned NULL is fine.
Maybe we do, i.e. where there is no value "-Dfoobar". So perhaps we
need to say that GetSystemProperty returns VMI_ERROR_NONE and sets the
the *valuePtr to NULL
Oliver Deakin wrote:
Tim Ellison wrote:
Geir Magnusson Jr. wrote:
Do we really have a problem? Or is it something else?
Last night, Gregory tested his fix, and I've build snapshots (r486417)
on x86 linux/win and x86_64 linux and spot checked with apps and such,
and things seem to work.
I'n
Alexey Varlamov wrote:
> Is there any reason to distinguish these cases? I suppose no, then
> returned NULL is fine.
Maybe we do, i.e. where there is no value "-Dfoobar". So perhaps we
need to say that GetSystemProperty returns VMI_ERROR_NONE and sets the
the *valuePtr to NULL if there is no valu
2006/12/13, Oliver Deakin <[EMAIL PROTECTED]>:
Tim Ellison wrote:
> Geir Magnusson Jr. wrote:
>
>> Do we really have a problem? Or is it something else?
>>
>> Last night, Gregory tested his fix, and I've build snapshots (r486417)
>> on x86 linux/win and x86_64 linux and spot checked with apps an
Tim Ellison wrote:
Geir Magnusson Jr. wrote:
Do we really have a problem? Or is it something else?
Last night, Gregory tested his fix, and I've build snapshots (r486417)
on x86 linux/win and x86_64 linux and spot checked with apps and such,
and things seem to work.
I'n posting the snapshot
Geir Magnusson Jr. wrote:
> Do we really have a problem? Or is it something else?
>
> Last night, Gregory tested his fix, and I've build snapshots (r486417)
> on x86 linux/win and x86_64 linux and spot checked with apps and such,
> and things seem to work.
>
> I'n posting the snapshots now to ~g
Do we really have a problem? Or is it something else?
Last night, Gregory tested his fix, and I've build snapshots (r486417)
on x86 linux/win and x86_64 linux and spot checked with apps and such,
and things seem to work.
I'n posting the snapshots now to ~geirm and will send a separate note
On 12/13/06, Geir Magnusson Jr. wrote:
Grrr. We had a thread last night "DRLVM broken on em64t" that you
should read.
Sorry, I hadn't read the discussion when I wrote about regression.
In the end, what I was asking is if/how the behavior of
GetSystemProperty() changed with our update to th
On 12/13/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
Grrr. We had a thread last night "DRLVM broken on em64t" that you
should read.
In the end, what I was asking is if/how the behavior of
GetSystemProperty() changed with our update to the property management
inside of DRLVM, and the rami
Grrr. We had a thread last night "DRLVM broken on em64t" that you
should read.
In the end, what I was asking is if/how the behavior of
GetSystemProperty() changed with our update to the property management
inside of DRLVM, and the ramifications of that.
Looking at Ollie's change in r486100,
22 matches
Mail list logo