Re: ISO extensible Eu - Holy Wars need not apply
Although what I actually meant was a way to make the actual apps in Eu
extensible, it's possible that a spec sheet could help extend the language
also.
You can look at it this way: Win32lib is in reality an extension to Eu,
written in Eu. If Win32lib were broken down into easily-digestible modules
(like Llama was going to be) and completely and totally spec'ed out (don't
panic David, I don't mean by you! LOL!), when someone wants to add to the
library, it becomes much easier. Windows only has about 17,000 API calls to
wrap. In dos, I think you're working more from a blank sheet because you're
not wrapping .dlls, but the principle is the same for the libraries.
I think the compiler should be a big help. Eu programmers will (or SHOULD)
be able to add .dlls written in Eu to extend the language. I have no
problem with using .dlls to extend the language, provided they're small and
fast.
However, coming up with an easy way to extend apps is also a priority I
think. That's a major draw for OOP. If you can do it without OOP, it's a
major coup because you avoid the baggage of OOP - the slowness and bloat.
It also makes the language attractive in yet another way to both newbies
and pros, because it's not only easier to extend and build on small
modules, it's less time consuming and less frustrating, and it makes code
reuse a possibility (though I've heard most pros don't like the idea of
code reuse even under OOP. I don't have that problem - I'm neither a pro
nor ambitious and energetic). It's pretty simple (but not easy) to set up
an administrative way to make applications extensible, which is why I ask
the question: would it be useful to add structure to these important
projects?
As an example of how the spec sheets would help newbies write better code,
let me use EuDesigner. If you use EuDesigner under Windows, you get a
standard output every time. If a newbie uses EuDesigner 25 times for 255
different programs, when she opens up an example program from JoeBob, who
is also using EuDesigner, she can immediately understand the event code,
and window creation calls. That's one less thing she has to worry about. If
the .eup file is included, she can open that right up in Eu, and add
buttons, or lists, or whatever to the app. If there was a spec sheet and
program flow chart with it, would it help newbies? I dunno. I SUSPECT it
would, but I don't know enough to tell you. Sure wouldn't hurt.
Question is: is it worth the hassle?
|
Not Categorized, Please Help
|
|
