Re: [Fwd: [7.4] DotNETConnect - code generator failure - wrapFunctionName]

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: [Fwd: [7.4] DotNETConnect - code generator failure - wrapFunctionName]

Ralf Propach
Boris Popov <[hidden email]> wrote:

> Next up, trying to generate code for an assembly, go through all the steps in the code generator, let it remove things that it wants to remove:
>
> TYPE CHECK OF ASSEMBLY:            InteropRANGERLib v1.0.0.0
> CREATED:                           March 5, 2006 16:10:28.245
>
> ITEMS KEPT:                        259
> ITEMS REMOVED:                     19
>
> TYPES KEPT:                        24
> TYPES ENTIRELY REMOVED:            1
>
> METHODS KEPT:                      235
>     CONSTRUCTORS:              19
>     PROPERTIES:                0
>     OTHERS:                    215
> METHODS REMOVED:                   18
>     CONSTRUCTORS:              0
>     PROPERTIES:                0
>     OTHERS:                    0

Hi Boris,
can you send the assembly to me, so that I can investigate what goes wrong?

>
> and try to generate code,
>
>
> Unhandled exception: Message not understood: #wrapFunctionName
> DotNETUtils.ByReferenceParameterDescription(Object)>>doesNotUnderstand:
> DotNETUtils.ByReferenceParameterDescription(DotNETUtils.ParameterDescription)>>writeCallbackWrappingTo:index:
>

There needs to be a method ByReferenceParameterDescription>>wrapFunctionName and I
think it should be
wrapFunctionName
        ^type wrapFunctionName

But would prefer to look at the generated code to check that it is correct.

>
> Subject:
> Re: [7.4] DotNETConnect woes

>
> Boris Popov wrote:
>
>> In the clean 7.4 image,
>>
>> - Trying to open DotNetConnect Code Generator raises an exception:
>>    Unhandled exception: Key not found:
>>    Dictionary>>keyNotFoundErrorFor:index:
>>    optimized [] in Dictionary>>at:
>>    Dictionary>>at:ifAbsent:
>>    Dictionary>>at:
[...]
>
> Okay maybe I should have been more patient and attached a fix (read:
> hack) for cases when assembly info does not contain DisplayName,
> whatever the reason for that could be.
>
> Cheers!
>
> -Boris
>
Thanks, I'll integrate that into the next DotNETConnect version.

> - Trying to open DotNetConnectBrowser raises an exception:
>    Unhandled exception: The identifier Net.URL has no binding
>    LiteralBindingReference(Object)>>error:
>    LiteralBindingReference(GeneralBindingReference)>>binding
>    LiteralBindingReference(GeneralBindingReference)>>value
>    DotNETUtils.AssemblyDescription class>>urlToFilename:
>    DotNETUtils.AssemblyDescription class>>fromInfo:

In 7.4 the class URL was moved from the namespace Net to OS.
So, Net.URL needs to be changed to URL. This affects the methods
AssemblyDescription class>>urlToFilename: and
AssemblyReference>>parse: . Then you will not need to load NetClients anymore.

When I have managed to generate a makefile that will also work under Visual Studio 2005,
I will release a new version of DotNETConnect.

Ralf