Re: [2/4] widl: Pass type attributes from write_array_tfs to write_pointer_description.
Dmitry Timoshkov <dmitry(a)baikal.ru> writes:
This allows to differentiate strings and write appropriate rpc type (FC_C_C[W]STRING instead of FC_[W]CHAR).
It also changes some pointers from UP to RP, that doesn't look right. -- Alexandre Julliard julliard(a)winehq.org
Alexandre Julliard <julliard(a)winehq.org> wrote:
This allows to differentiate strings and write appropriate rpc type (FC_C_C[W]STRING instead of FC_[W]CHAR).
It also changes some pointers from UP to RP, that doesn't look right.
I don't see any changes in server_c.c and server_s.c in dlls/rpcrt4/tests, do you see this somewhere else? -- Dmitry.
Dmitry Timoshkov <dmitry(a)baikal.ru> writes:
Alexandre Julliard <julliard(a)winehq.org> wrote:
This allows to differentiate strings and write appropriate rpc type (FC_C_C[W]STRING instead of FC_[W]CHAR).
It also changes some pointers from UP to RP, that doesn't look right.
I don't see any changes in server_c.c and server_s.c in dlls/rpcrt4/tests, do you see this somewhere else?
In many of the generated proxy files, in actxprxy for instance. -- Alexandre Julliard julliard(a)winehq.org
Alexandre Julliard <julliard(a)winehq.org> wrote:
This allows to differentiate strings and write appropriate rpc type (FC_C_C[W]STRING instead of FC_[W]CHAR).
It also changes some pointers from UP to RP, that doesn't look right.
I don't see any changes in server_c.c and server_s.c in dlls/rpcrt4/tests, do you see this somewhere else?
In many of the generated proxy files, in actxprxy for instance.
As far as I can see new behaviour matches what midl generates, for instance for wireBSTR/SAFEARR_BSTR. -- Dmitry.
Dmitry Timoshkov <dmitry(a)baikal.ru> writes:
Alexandre Julliard <julliard(a)winehq.org> wrote:
This allows to differentiate strings and write appropriate rpc type (FC_C_C[W]STRING instead of FC_[W]CHAR).
It also changes some pointers from UP to RP, that doesn't look right.
I don't see any changes in server_c.c and server_s.c in dlls/rpcrt4/tests, do you see this somewhere else?
In many of the generated proxy files, in actxprxy for instance.
As far as I can see new behaviour matches what midl generates, for instance for wireBSTR/SAFEARR_BSTR.
It generates FC_UP here (midl 7.0). Is it different in newer versions? -- Alexandre Julliard julliard(a)winehq.org
Alexandre Julliard <julliard(a)winehq.org> wrote:
This allows to differentiate strings and write appropriate rpc type (FC_C_C[W]STRING instead of FC_[W]CHAR).
It also changes some pointers from UP to RP, that doesn't look right.
I don't see any changes in server_c.c and server_s.c in dlls/rpcrt4/tests, do you see this somewhere else?
In many of the generated proxy files, in actxprxy for instance.
As far as I can see new behaviour matches what midl generates, for instance for wireBSTR/SAFEARR_BSTR.
It generates FC_UP here (midl 7.0). Is it different in newer versions?
I don't see differences between the code generated by midl shipped with PSDK 7.1 (midl 7.00.0555) and Visual Studio Express 12.0 (midl 8.00.603). -- Dmitry.
Dmitry Timoshkov <dmitry(a)baikal.ru> writes:
Alexandre Julliard <julliard(a)winehq.org> wrote:
> This allows to differentiate strings and write appropriate rpc type > (FC_C_C[W]STRING instead of FC_[W]CHAR).
It also changes some pointers from UP to RP, that doesn't look right.
I don't see any changes in server_c.c and server_s.c in dlls/rpcrt4/tests, do you see this somewhere else?
In many of the generated proxy files, in actxprxy for instance.
As far as I can see new behaviour matches what midl generates, for instance for wireBSTR/SAFEARR_BSTR.
It generates FC_UP here (midl 7.0). Is it different in newer versions?
I don't see differences between the code generated by midl shipped with PSDK 7.1 (midl 7.00.0555) and Visual Studio Express 12.0 (midl 8.00.603).
Do you really get FC_RP pointers in there? Did you build with the Wine headers? -- Alexandre Julliard julliard(a)winehq.org
Alexandre Julliard <julliard(a)winehq.org> wrote:
> > This allows to differentiate strings and write appropriate rpc type > > (FC_C_C[W]STRING instead of FC_[W]CHAR). > > It also changes some pointers from UP to RP, that doesn't look right.
I don't see any changes in server_c.c and server_s.c in dlls/rpcrt4/tests, do you see this somewhere else?
In many of the generated proxy files, in actxprxy for instance.
As far as I can see new behaviour matches what midl generates, for instance for wireBSTR/SAFEARR_BSTR.
It generates FC_UP here (midl 7.0). Is it different in newer versions?
I don't see differences between the code generated by midl shipped with PSDK 7.1 (midl 7.00.0555) and Visual Studio Express 12.0 (midl 8.00.603).
Do you really get FC_RP pointers in there? Did you build with the Wine headers?
I was testing actxprxy_activscp.idl, it doesn't build with Wine headers, so I had to simplify the dependant .idl files quite a bit. I could retry tomorrow if you think that I may have screwed something during simplification. -- Dmitry.
participants (2)
-
Alexandre Julliard -
Dmitry Timoshkov