From: Dieter Wilhelm <dieter@duenenhof-wilhelm.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: VAX/VMS
Date: Fri, 24 Nov 2006 22:06:24 +0100 [thread overview]
Message-ID: <87y7q01rn3.fsf@hans.local.net> (raw)
In-Reply-To: <f7ccd24b0611241113t835899cpbc7824bcfe0b5a4d@mail.gmail.com> (Juanma Barranquero's message of "Fri\, 24 Nov 2006 20\:13\:30 +0100")
"Juanma Barranquero" <lekktu@gmail.com> writes:
> On 11/23/06, Per Abrahamsen <abraham@dina.kvl.dk> wrote:
>
>> VAX/VMS had a strongly typed file system
Could you briefly describe what a strongly typed file system is,
sorry?
Is this analogous to a "strongly typed" programming language? Is in
this sense C a strongly typed language? One must declare the type and
can interchange--with some exceptions--only same types. Would Lisp be
a weakly typed language, because the type information is stored in the
data itself?
>
> This is a feature. As it was its automatic versioning of files.
I read Vista is going to have something similar.
>
>> It also had a really
>> obscure syntax for file names, using []:. among other special
>> characters.
>
> Obscure only from another system's mindset. There was nothing obscure
> in its filename syntax from my POV.
>
>> And a zillion different kind of hardwired interacting
>> privileges that meant that ordinary users rarely were able to do what
>> they want, but hackers could do anything as there were always some
>> obscure path from "may use the printer privilege" to "can overwrite
>> system files privilege".
>
> As if that didn't ever happen on Unix, did it? :-)
>
>> The editors were EDT and later TPU. They were much better than vi, I
>> have to give them that. You can suffer them in Emacs with M-x
>> edt-emulation-on <ref> or M-x tpu-edt <ret>. (TPU was really a system
>> for writing editors in).
I really like Emacs but I think vi(m) is not so bad, after all.
>
> The usual TPU editor was called EVE (Extensible Vax Editor).
>
>> Some people liked VAX/VMS, typically the same who preferred Wirth
>> Pascal over K&R C. For the rest of us, Ultrix was a much more
>> productive environment, once you had installed Emacs in it.
>
> Thought I'm no Pascal freak, about the only language I wouldn't prefer
> over K&R C is BASIC...
>
For what it's worth, both of you can go on indefinitely, I like to
read about these things 8-)
> /L/e/k/t/u
--
Best wishes
H. Dieter Wilhelm
Darmstadt, Germany
next prev parent reply other threads:[~2006-11-24 21:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 17:06 Debian/GFDL Nicolas Neuss
2006-11-10 22:01 ` Debian/GFDL Eli Zaretskii
2006-11-10 22:14 ` Debian/GFDL David Hansen
2006-11-13 10:49 ` Debian/GFDL Ismael Valladolid Torres
2006-11-13 12:33 ` Debian/GFDL Juanma Barranquero
2006-11-13 15:04 ` Debian/GFDL Ismael Valladolid Torres
2006-11-13 15:09 ` Debian/GFDL Juanma Barranquero
2006-11-13 16:11 ` Debian/GFDL Ismael Valladolid Torres
2006-11-13 17:56 ` Debian/GFDL Gian Uberto Lauri
[not found] ` <mailman.509.1163443911.2155.help-gnu-emacs@gnu.org>
2006-11-14 2:09 ` Debian/GFDL Will Parsons
2006-11-13 22:21 ` Debian/GFDL Dieter Wilhelm
2006-11-13 22:33 ` Debian/GFDL Juanma Barranquero
[not found] ` <mailman.528.1163456488.2155.help-gnu-emacs@gnu.org>
2006-11-23 10:38 ` VAX/VMS (was: Re: Debian/GFDL) Per Abrahamsen
2006-11-24 19:13 ` Juanma Barranquero
2006-11-24 21:06 ` Dieter Wilhelm [this message]
[not found] ` <mailman.417.1163196096.2155.help-gnu-emacs@gnu.org>
2006-11-11 13:50 ` Debian/GFDL David Kastrup
2006-11-11 15:30 ` Debian/GFDL David Hansen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y7q01rn3.fsf@hans.local.net \
--to=dieter@duenenhof-wilhelm.de \
--cc=help-gnu-emacs@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).