Simply and completely - no.
ISE Eiffel is .NET compatible but not .NET compliant.
The .NET visibility model is simpler than the Eiffel model. (You can not have C++ friends either)
Eiffel access and visibility rules do not extend beyond the assembly - so it is all or nothing. Given that nothing is not very useful ... You get all.
Sent via BlackBerry® from Vodafone
-----Original Message-----
From: "galuszkiewicz" <
[hidden email]>
Date: Sat, 10 Oct 2009 17:02:29
To: <
[hidden email]>
Subject: [eiffel_software] Feature visibilty levels in .NET
Hi,
I'm playing with simple library written in Eiffel and compiled to .NET target. I've created a C# client app which uses that library.
I noticed that all features defined in my Eiffel classes are "public" in .NET - is there any way of setting that and indicating which features should be generated as "internal" ???
Greetings,
Piotr
[Non-text portions of this message have been removed]
