all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Subject: Re: Program structure of Pstricks, what is its basic structure?
Date: 24 Feb 2004 09:39:44 +0100	[thread overview]
Message-ID: <x5ekskna5r.fsf@lola.goethe.zz> (raw)
In-Reply-To: 42414174.0402240015.47937b1d@posting.google.com

crashedandburnt1@hotmail.com (Crashedandburnt) writes:

> > And Dr Van Zandt made a civilized comment without calling you any
>                           ^^^^^^^^^ I guess you do not understand
>                           the meaning of the word "assinine".
> > names.  Which is more than can be said for your prior post!

If you put quotation marks about a word, you should use the original
spelling.  Timothy is not illiterate.  And he applied that wording to
your posting, not to you.  And your posting more than deserved that
name.

> > He has offered documentation which is verifiable:  pstricks.doc.
> > 
> > > Although a comment per line of code is not too much,I do not hold
> > > your package to this standard.
> > 
> > A comment per line of code is certainly far too much!  Any reasonably
> > competent programmer doesn't need such handholding; comments are only
> > needed for the nob-obvious sections of code.
> 
> If that is the case why is their any traffic for questions, many
> times basic questions, on this newsgroup at all???? Do a count of
> questions in say 3 week period. There is already a tex book.

There are few questions about PStricks here.

> That is why I stated it to prevent misunderstanding. Some people
> can't take reasonable criticism and mistake it for accusation.

There was no reasonable criticism I remember.

> But get to the point, circumvent the thorny issues. It is the last
> sentence:
> 
> In the coming days, the ability of people to explain the subject of
> this thread will itself testify how well it is documented.
> 
> Show me the votes by giving the explanation, or accept the
> conclusion that documentation is indeed poor.

Uh, the programmer documentation for PStricks is pretty much ok.  The
user level documentation consists of 4 files documenting an earlier
version of it, and 2 files documenting most of the changes since then.

This state of affairs is indeed somewhat dissatisfactory, and has been
such for several years.  It is, however, hardly anything you could
_demand_ from the original author.  While he probably would be the
first pick for commissioning a manual about it, you need not expect
that he should be the cheapest one, were he willing to accept the
assignment.  Why should he, being best qualified?  And to expect that
he should be compelled to do this for free is ridiculous.

Nobody is in a position to demand such a thing, and least of all some
foul-mouthed slanderer hiding behind a pseudonym.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum
UKTUG FAQ: <URL:http://www.tex.ac.uk/cgi-bin/texfaq2html>

  reply	other threads:[~2004-02-24  8:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3n07dv5xj.fsf@pdrechsler.fqdn.th-h.de>
     [not found] ` <QY8DY60K38039.536875@Gilgamesh-Frog.org>
     [not found]   ` <c1a78u$6bm$01$1@news.t-online.com>
2004-02-23  3:53     ` Program structure of Pstricks, what is its basic structure? Crashedandburnt
2004-02-23 10:52       ` Giuseppe Bilotta
2004-02-24  0:36         ` Crashedandburnt
2004-02-23 14:18       ` Tim McNamara
2004-02-23 14:52       ` Timothy Van Zandt
2004-02-24  0:04         ` Crashedandburnt
2004-02-24  3:10           ` Tim McNamara
2004-02-24  7:49             ` Brooks Moses
2004-02-24  8:15             ` Crashedandburnt
2004-02-24  8:39               ` David Kastrup [this message]
2004-02-24 16:28                 ` R. H. Allen
2004-02-24  3:21           ` David Kastrup
2004-02-24  8:51             ` Crashedandburnt
2004-02-24  9:20               ` David Kastrup
2004-02-24 19:18               ` Tim McNamara
2004-02-24 15:08           ` Paul Thompson
2004-02-23 15:49       ` Timothy Van Zandt
2004-02-23 17:34         ` Donald Arseneau
2004-02-23 17:54       ` R. H. Allen
2004-02-24 15:23       ` Cameron Laird

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x5ekskna5r.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.