Tcl - .NET DLLs - can they be used... ?

Author

.NET DLLs - can they be used... ?

youra.turceninoff@gmail.com

2006-10-01, 7:05 pm

Hi.

Just back to TCL after a few years in a role which didn't need it...

I've always been a little sketchy on the use of external DLLs under
Windows, and here I'm up against a bit of a brick wall - I have some
vendor supplied DLLs that control a fancy bit of external test kit, but
they only define the interface in a .NET manner - can DLLs intended for
use in this way be used in TCL?

I've tried various things usinf ffidl and another DLL loader, but not
having much luck - anyone have any thoughts - I'm also worried that the
return structures are complex in some cases, and the simpler DLL
loaders only appear to support simple return types.

Thanks,

Youra.

Michael Schlenker

2006-10-01, 7:05 pm

youra.turceninoff@gmail.com schrieb:
> Hi.
>
> Just back to TCL after a few years in a role which didn't need it...
>
> I've always been a little sketchy on the use of external DLLs under
> Windows, and here I'm up against a bit of a brick wall - I have some
> vendor supplied DLLs that control a fancy bit of external test kit, but
> they only define the interface in a .NET manner - can DLLs intended for
> use in this way be used in TCL?
>
> I've tried various things usinf ffidl and another DLL loader, but not
> having much luck - anyone have any thoughts - I'm also worried that the
> return structures are complex in some cases, and the simpler DLL
> loaders only appear to support simple return types.
>
One option would maybe be to use tclcsharp, a reimplementation of Tcl
with C#, which might simplify interfacing with .NET stuff...

http://sourceforge.net/projects/tclcsharp

Michael

Youra

2006-10-02, 4:23 am

Thanks for the link Michael - that looks just the trick, but also,
unfortunately, looks like a dead-end project (i.e. the author himself
says it was just an experiment to prove a point, and has several
fundamental non-functionalities and instabilities.....)

I'll be getting in contact with the DLL vendor today to see if they
have easrlier versions that use more normal 'C' conventions - Maybe
crtitcl or SWIG could help - but then I'd at least need a minimal C
compiler installation.....

thanks,

Y.

Michael Schlenker wrote:
> youra.turceninoff@gmail.com schrieb:
> One option would maybe be to use tclcsharp, a reimplementation of Tcl
> with C#, which might simplify interfacing with .NET stuff...
>
> http://sourceforge.net/projects/tclcsharp
>
> Michael

Earl Greida

2006-10-02, 4:23 am

"Youra" <youra.turceninoff@gmail.com> wrote in message
news:1159770911.017406.98220@c28g2000cwb.googlegroups.com...
> Thanks for the link Michael - that looks just the trick, but
> also, unfortunately, looks like a dead-end project (i.e. the
> author himself says it was just an experiment to prove a point,
> and has several fundamental non-functionalities and instabilities.....)
>
> I'll be getting in contact with the DLL vendor today to see if
> they have easrlier versions that use more normal 'C' conventions
> - Maybe crtitcl or SWIG could help - but then I'd at least need a
> minimal C compiler installation.....
>

You should ask the vendor why they do not provide Tcl APIs.

Sponsored Links