Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!asuvax!mcdphx!varese.UUCP!kjj
From: kjj@varese.UUCP (Kevin Johnson)
Newsgroups: comp.lang.misc
Subject: Re: Anyone want to design a language?
Message-ID: <12507@mcdphx.phx.mcd.mot.com>
Date: 17 Feb 90 14:40:19 GMT
References: <22569:05:10:24@stealth.acf.nyu.edu>
Sender: listen@mcdphx.phx.mcd.mot.com
Reply-To: kjj@varese.UUCP (Kevin Johnson)
Organization: Motorola Microcomputer Division, Tempe, Az.
Lines: 30

In article <22569:05:10:24@stealth.acf.nyu.edu> brnstnd@stealth.acf.nyu.edu (Dan Bernstein) writes:
>So what do you want in a compiled, imperative, perhaps object-oriented
>language? Take C as a starting point for good ideas and feel free to
>use parts of any other language. Remember: This isn't Ada. If it gets
>too complicated, trash it. Simple is beautiful. Modular design is
>beautiful. And above all, remember that this is going to be a language
>people can actually like.

Rhetorical question: Aren't you talking about C++?
Semi-rhetorical question: What would be this language's intended use?

1. How about string operators.
	I hate handling allocing of space for something silly like strings...

2. Ability to dynamically define new operators

3. Ability to use existing C libraries and headers.
	Otherwise, I want:
		a. screen handling poop
		b. internet poop
		b. X poop
		c. :-)
	Seriously, I would consider the ability to link in existing
	libraries, one way or another, an absolute must.


#include <standard_disclaimer>
.-----------------------------------------------------------------------------.
| Kevin Johnson                                      ...!mcdphx!QIS1!kjj      |
| QIS System Administrator  Motorola MCD             kjj@phx.mcd.mot.com      |