1. RE: about .NET
Sorry, accidently posted that message before I finished writing it.
Continuing on now:
I think Euphoria needs a way to interoperate with .NET. It doesn't have to
actually make .NET applications, but it should have a function similar to
open_dll for .NET. This way the newest features of the next version of windows
can be used in .NET application, and if it is done right, euphoria will have the
whole .NET Framework to use. This would add a ton of great features to euphoria,
such as web services, windows forms, ADO.NET (database access), etc.
So, basically, I think Euphoria should interoperate with .NET as much as it
currently does with C.
Thanks for reading this,
Phil
2. RE: about .NET
Philip Deets wrote:
>
> Sorry, accidently posted that message before I finished writing it.
>
> Continuing on now:
>
> I think Euphoria needs a way to interoperate with .NET. It doesn't have to
> actually
> make .NET applications, but it should have a function similar to open_dll for
> .NET.
> This way the newest features of the next version of windows can be used in
> .NET application,
> and if it is done right, euphoria will have the whole .NET Framework to use.
> This
> would add a ton of great features to euphoria, such as web services, windows
> forms,
> ADO.NET (database access), etc.
>
> So, basically, I think Euphoria should interoperate with .NET as much as it
> currently
> does with C.
This would be a problem. .NET is a totally different architecture. There is
backward compatibility (you can call 'unsafe' old, native DLLs and routines), but
the other way around isn't possible. The only possibility is creating a
.NET-version of Euphoria, that compiles Euphoria-code into
.NET-assemblies/applications.
The most important question here is: what will we call it? 
A. Euphoria.NET
B. E# (pronounce: e sharp)
C. Something else
Vote for the name you want (or suggest a new name) at UBoard
(http://uboard.proboards32.com) in the 'General Board'.
--
tommy online: http://users.pandora.be/tommycarlier
Euphoria Message Board: http://uboard.proboards32.com
3. RE: about .NET
Tommy Carlier wrote:
>
> Philip Deets wrote:
> >
> > Sorry, accidently posted that message before I finished writing it.
> >
> > Continuing on now:
> >
> > I think Euphoria needs a way to interoperate with .NET. It doesn't have to
> > actually
> > make .NET applications, but it should have a function similar to open_dll
> > for .NET.
> > This way the newest features of the next version of windows can be used in
> > .NET application,
> > and if it is done right, euphoria will have the whole .NET Framework to use.
> > This
> > would add a ton of great features to euphoria, such as web services, windows
> > forms,
> > ADO.NET (database access), etc.
> >
> > So, basically, I think Euphoria should interoperate with .NET as much as it
> > currently
> > does with C.
>
> This would be a problem. .NET is a totally different architecture. There is
> backward
> compatibility (you can call 'unsafe' old, native DLLs and routines), but the
> other
> way around isn't possible. The only possibility is creating a .NET-version of
> Euphoria,
> that compiles Euphoria-code into .NET-assemblies/applications.
>
> The most important question here is: what will we call it?
> A. Euphoria.NET
> B. E# (pronounce: e sharp)
> C. Something else
>
> Vote for the name you want (or suggest a new name) at UBoard (<a target=_top
> href="http://uboard.proboards32.com">http://uboard.proboards32.com</a>)
> in the 'General Board'.
>
> --
> tommy online: <a target=_top
> href="http://users.pandora.be/tommycarlier">http://users.pandora.be/tommycarlier</a>
> Euphoria Message Board: <a target=_top
> href="http://uboard.proboards32.com">http://uboard.proboards32.com</a>
>
Maybe euphoria can steal some of the source code from the Mono project to help
with running .NET.
If I'm offbase and you are right that euphoria needs to actually be .NET. Then
I vote for Euphoria.NET as the name.
Phil
