[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[mgp-users 01174] Re: Sam's Improvements; my MGP macro processor
- To: Chris Ball <chris@void.printf.net>
- Subject: [mgp-users 01174] Re: Sam's Improvements; my MGP macro processor
- From: Sam Steingold <sds@gnu.org>
- Date: 03 Jun 2003 10:04:05 -0400
- Cc: mgp-users@mew.org
- Delivered-to: mailing list mgp-users@mew.org
- In-reply-to: <>
- Mail-copies-to: never
- Mailing-list: contact mgp-users-help@mew.org; run by ezmlm
- References: <> <> <> <> <> <>
- Reply-to: sds@gnu.org
- User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50
Chris,
> * In message <>
> * On the subject of "Re: [mgp-users 01172] Re: Sam's Improvements; my MGP macro processor"
> * Sent on Tue, 03 Jun 2003 05:35:54 +0100
> * Honorable Chris Ball <chris@void.printf.net> writes:
>
> Your argument that we could use a frontend to emulate the current
> syntax is specious -- as you point out, the current syntax is
> ambiguous. How would we fit it on top of a representation that
> actively forbids this?
A perl script that converts the ambiguous but terse syntax into the
unambiguous XML abomination will have to disambiguate the ambiguities
in a _well_ _documented_ way.
A user who does not like the way it disambiguates the ambiguities, can
modify the script or write his own or commission someone to write a
script he wants.
Or just use the unambiguous syntax directly, like I will, even if I
like the way the script disambiguates the ambiguities.
> > IMNSHO, people who say "I would rather lose the complete unambiguity
> > in exchange for..." [doesn't matter what!] give the bad name to the
> > profession of a Computer Scientist or Software Engineer or whatever
> > you call it.
>
> I'll go half way with you.
Good - so I am half done with converting you :-)
> People who are willing to lose complete unambiguity for a price give a
> bad name to Computer Science; people who are willing to make their
> users write XML give a bad name to Software Engineering.
I am _not_ saying that the user should be forced to write XML.
I _am_ saying that he should be given an option of an absolutely
unambiguous format, e.g., XML, _plus_ a GUI WYSIWYG front-end - or at
least a script that converts the current input to the unambiguous one.
I repeat that the unambiguous format should be there _not_ just for
debugging - it should be expected that some users will actually use it
directly.
> Our dilemma as programmers is to decide which profession we'd rather
> insult more.
it's a bad soldier who does not want to be a general.
it's a bad software engineer who does not think of himself as a
computer scientist.
--
Sam Steingold (http://www.podval.org/~sds) running RedHat9 GNU/Linux
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html>
The world will end in 5 minutes. Please log out.