)
I don't think anything has been resolved. Lynn has an idea on how to improve
programmer productivity we just need to agree on where to start, the goal has
already been set.
> > IMO the effort should be in the design of
> > the programmer interface and the logic for
> > proving the code complete and unambiguous.
>
> I would certainly like some new programmer interfaces. For years I've
> wanted a tool that allowed me to graphically create a system flowchart,
> then associate each box with an appropriate piece of software (or a
> subsystem), and let the tool "compile" my finished system. I like
> flowcharts.
That is part of the challenge of Lynn's idea, design a new programmer
interface. So far everyone has been arguing about the compiler where very
little benefit will be obtained.
> As for proving the code, good idea. I have no knowledge at all in this
> field. I've seen it mentioned from time to time in various articles but
> never defined or explained. Anybody want to enlighten me?
It is called logic programming. Look at Prolog.
> Okay, Lynn, here's my list of things you should talk about:
>
> -- open source
This is a given for this project.
> -- code optimization
This is low priority for starting this project.
> -- HLL design (including English as one alternative)
We do need a good definition for the language we are going to use.
> -- HLL implementation ("dope vectors" etc)
This has nothing to do with programmer productivity, the compiler will handle
the details.
> -- proving the code
Someone needs to start writing some Prolog code.
> What have I missed?
I sure you have missed something. We need to define the big picture of the
project and then set priorities for the various parts.
As I see it these are the parts.
1.programmer interface
2.data base 3. completion logic 4.syntax/semantic checks
5.testing
6.compiler
To start to prove that this will work you need to start at the top and work
your way down, in this case bottom up will not get you anything because the
benefits occur at the top. The data base is not interesting because there are
a lot of choices. The testing part as I see it would be an interpreter and
some of the smarts from the completion logic, I think this should be done at a
later stage of the development. The syntax/semantic checking is needed early
as well as the completion logic. The language and the interface are required
now. The compiler can be anyone of the compilers available now the output can
be done in any language, a complete project would compile directly to
executable but is not needed until later in the project.
So what I see as the priorities are
1.programmer interface - which includes the language definition
4.syntax/semantic checks
3. completion logic
5.testing
2.data base
6.compiler
--
Robert Blair
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 06 |
August |
2003 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
