Re: More Etymology!

On Jan 31, 2:43 pm, "Peter T. Daniels" <gramma...@xxxxxxxxxxx> wrote:

I stopped, long ago, looking at your messages; I see them only when
someone else has posted meanwhile in one of your threads. I did check
the catalogs of the libraries I have access to, and the only one that
owns the book keeps it "offsite," meaning that one has to plan in
advance to request it. As I rarely know three days in advance that I
will be traveling in to the city to visit the library, that is not an
option for me.

But you always ask me again what is so special about Göbekli Tepe.
Either I ignore your question, because you don't read my reply anyway,
or then I answer it, and what happens? you ignore it, as you do again.
Meanwhile I see the pattern. Let me explain. I love to go window
shopping, so I am always up-to-date, with computers, digital cameras,
etc. When I actually buy a computer or a digital camera they are new
for half a year, then new models appear on the market, and sooner
or later my devices will be out-dated. Same happens with a book.
It's new when freshly released, but then new scientific insights make
it grow old and older. You fear that process. You can't have your book
out-dated. You hold up time by ignoring new insights about early
and earliest writing. This is the true reason for your absurd behaving
when it comes to Derk Ohlenroth, and when it comes to Göbekli Tepe.

There is no reason whatsoever to suppose that the symbols(?) found at
GT are "writing." By your own testimony, they are isolated glyphs.

Klaus Schmidt speaks of hieroglyphs: in the case of thirteen small
pictograms, which I listed up in a previous message. Your above
self-induced blindness forbids you to quote that passage. You
can't but undo it. And yes, they are writing. Klaus Schmidt says
these hieroglyphs are conveying messages that have once been
readable, and may perhaps be readable again one time. Ironically,
Derk Ohlenroth published his book in 1996, and Klaus Schmidt
began excavating Göbekli Tepe in about the same time, the time
when you published your book. You can't look at their work because
they make your book age, your claim on fame go lame. You are
wrong. Face the new insights, and actualize your book. It's worth it.

As I said, stop intermingling your responses. I have no idea what
"killrating" is, nor why anyone would bother doing it.

You are "forced" to use Google you told us, and so you know well
what I mean by killrating.

Now somebody killrate my message. Tell me that you lack
arguments and can't cope with me on a scientific level.



.

Relevant Pages

  • Re: build faster
    ... Which is faster right now, locating testing and learning the library, writing your own, or just coding from scratch. ... In addition to writing reuseable code you should be writing expandable code that is backward compatible. ... Now I see a lot of work other programmers have done where there is no OO, there often are no functions, this is all embedded calls and includes in html. ... A competent programmer seldom starts from scratch and has libraries of code which can be used on almost any project ...
    (comp.lang.php)
  • Re: use of backward single quote in procedure names, was: DST (summer time) offset
    ... I admit to writing certain classes of thing in BASIC and other classes ... that gets you beyond the standard C libraries. ... RISC OS language discussion) and I'll bother to answer. ... has no pre-run-time syntax checking ...
    (comp.sys.acorn.programmer)
  • Re: ML vs. Lisp
    ... would be better off writing *ML, or are you being ironic again? ... Look at LAPACK, FFTW, GLU and GTK from OCaml for example. ... I don't use many C libraries and the ones ... Use a common language run time like .NET. ...
    (comp.lang.functional)
  • Re: modular programming in Forth
    ... writing larger systems, like Netscape, the Linux kernel, Emacs, gcc. ... Concerning dynamically linked libraries: how do they help with name ... claim that the lack of a module system is the reason for Forth's ... No way to avoid collisions of program-generated exception numbers. ...
    (comp.lang.forth)
  • Re: Fn Defn Style
    ... When I'm writing something alone, I do find that the benefits of heavy ... I actually find it easier to have separate functions in separate files ... Even when writing applications [I tend to work on libraries more] I ... Like we recently wrote an app with crypto and DB functionality. ...
    (comp.lang.c)