Re: Coming real soon!
This is a multi-part message in MIME format.
------=_NextPart_000_004A_01C112AC.1AACED60
charset="iso-8859-1"
Has this comment has been totally misconstrued? When compared to other =
languages, or specifically their Win32 capabilities, I think Euphoria =
currently has set a very ad-hoc precedent. To cut the shit, the API is =
effectively a backbone segment of every Win32 language; this is =
indisputable. And you cannot statically link functions with Euphoria, =
only dynamically; so although this is not really the issue it =
effectively means every program must include the API definition before =
it can do anything else. What Euphoria needs is a base API library, from =
which every other windows library is built apon. From the base comes =
protocol. I agree these problems are not specifically Euphoria Language =
issues but software implentation issues. But comeon...
=20
Although WIN32Lib is a seperate issue, it is an example of a very =
different (high level) protocol by which to communicate with the API. =
But how about a bit of creative engineering? With a Win32 base library =
covering (hopefully the entire) API, Win32Lib could just include this =
before declaring its own routines for (in my opinion) superior =
engineered code. Right now anyone who wants to get lower than Win32Lib =
has to wade through API definitions and tedious copy/paste activities. I =
know, I have half the damn API plastered accross my hard drive which I =
add to as needed. Although it is beside to point to argue libraries are =
NOT part of the Euphoria Language, API protocol is usually semi-DEFINED =
in other langauges before you actually "include libraries". Yes, ok its =
more complex than that; but in currently in Euphoria its 20x more =
complex than that. Does everyone who wants to step ahead into the more =
complex and faster waters beyond Win32lib have to spend hours upon hours =
manually creating the masterpiece of API definition?
=20
Still, besides how far off the point this thread is going to be =
argued, who can criticise Bernie here for what he's doing? Who can =
possibly argue that Euphoria(Win32) does not need this library? Hello?
=20
I fullheartedly support Bernie with this brave endeavour. If completed =
I will definitely be "including" it in my code. I believe it is a =
positive step forward to simplify the first aspect of low level (or any =
level-library) programming for Euphoria.
=20
Francis
So you think Euphoria should have ability to include *.h header files.
I agree with this, still writing define_c_func and open_dll is tiring.
Martin
------=_NextPart_000_004A_01C112AC.1AACED60
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV><FONT face=3DArial size=3D2>Has this comment has been totally =
misconstrued?=20
When compared to other languages, or specifically their Win32 =
capabilities, I=20
think Euphoria currently has set a very ad-hoc =
precedent. To=20
cut the shit, the API is effectively a backbone segment of =
every=20
Win32 language; this is indisputable. And you cannot statically link =
functions=20
with Euphoria, only dynamically; so although this is not really the =
issue it=20
effectively means every program must include the API definition before =
it can=20
do anything else. What Euphoria needs is a base API library, from =
which every=20
other windows library is built apon. From the base comes protocol. I =
agree=20
these problems are not specifically Euphoria Language issues but =
software=20
implentation issues. But comeon...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Although WIN32Lib is a seperate =
issue, it is an=20
example of a very different (high level) protocol by which to =
communicate=20
with the API. But how about a bit of creative engineering? With a =
Win32=20
base library covering (hopefully the entire) API, Win32Lib could just =
include=20
this before declaring its own routines for (in my opinion) =
superior=20
engineered code. Right now anyone who wants to get lower than Win32Lib =
has to=20
wade through API definitions and tedious copy/paste activities. I =
know, I have=20
half the damn API plastered accross my hard drive which I add =
to as=20
needed. Although it is beside to point to argue libraries are NOT part =
of the=20
Euphoria Language, API protocol is usually semi-DEFINED in other =
langauges=20
before you actually "include libraries". Yes, ok its more complex than =
that;=20
but in currently in Euphoria its 20x more complex than that. Does =
everyone who=20
wants to step ahead into the more complex and faster waters=20
beyond Win32lib have to spend hours upon hours manually creating =
the=20
masterpiece of API definition?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Still, besides how far off the point =
this thread=20
is going to be argued, who can criticise Bernie here for what he's =
doing? Who=20
can possibly argue that Euphoria(Win32) does not need this library?=20
Hello?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I fullheartedly support Bernie with =
this brave=20
endeavour. If completed I will definitely be "including" it in my =
code. I=20
believe it is a positive step forward to simplify the first aspect of =
low=20
level (or any level-library) programming for Euphoria.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Francis</FONT></DIV></BLOCKQUOTE>
<DIV style=3D"MARGIN-RIGHT: 0px"><FONT face=3D"Arial CE" size=3D2>So you =
think=20
Euphoria should have ability to include *.h header files.</FONT></DIV>
<DIV style=3D"MARGIN-RIGHT: 0px"><FONT face=3D"Arial CE" size=3D2>I =
agree with this,=20
still writing define_c_func and open_dll is tiring.</FONT></DIV>
<DIV style=3D"MARGIN-RIGHT: 0px"> </DIV>
<DIV style=3D"MARGIN-RIGHT: 0px"><FONT face=3D"Arial CE" =
size=3D2> =20
------=_NextPart_000_004A_01C112AC.1AACED60--
|
Not Categorized, Please Help
|
|
