From: vasco@icpnet.pl (Andrzej Popielewicz)
Subject: [TUHS] Borland's C++ BuilderX, Personal Edition
Date: Thu, 21 Jul 2005 21:45:24 +0200 [thread overview]
Message-ID: <42DFFB54.80205@icpnet.pl> (raw)
In-Reply-To: <20050721164429.60aa8811.jrvalverde@cnb.uam.es>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]
Użytkownik José R. Valverde napisał:
>Looks like overkill to me. It made lots of sense way back then, but as you
>are speaking of an X86 port and you can assume an ANSI terminal to be the
>default and available, you may as well (at least as a start) do without
>termcap and terminfo (BTW I'd bet you don't need support for almost none
>of those ancient terminals).
>
I do not need curses or termcap or terminfo to work under simulated pdp
environment via apout in Coherent. As I said I can build
everything(using V7 make,cc ans as), it means I can work, and I do not
need ANSI terminal (if You have meant true VT100 terminal, and not
TERM=vt100 on PC, BTW apout for version 7 assumes as default TERM=vt100
). I was meaning building in pdp environment running in Coherent, and
not building in Coherent via for example a crosscompiler or so.
One needs termcap or terminfo if one wants to port more sophisticated
tools like vi etc.
>
>What you can get is then a simpler screen-oriented text editor which can
>easily be ported and then used as a bootstrap to port more advanced tools.
>
>Namely, S from 'A Software Tools Sampler' by Webb Miller. I ported and used
>it on both V6 and V7, and still use it on V7 on SIMH. Neat, small, easy to
>port, usage alike vi, but much simpler... And comes with some other
>interesting tools (actually my first involvement with that code was to have a
>unix-like toolkit on eraly VMS long, long ago).
>
>The code is available on the Net, but I'm including it here as an attachment
>as it is not that big (52K).
>
> j
>
>
Great, I will try it out. I have already tested succesfully more_v7 ,
which I obtained from Tim.
Thanks. I will let You know how it works.
Andrzej
next prev parent reply other threads:[~2005-07-21 19:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 15:41 James Falknor
2005-07-10 20:21 ` Andrzej Popielewicz
2005-07-10 20:25 ` Wilko Bulte
2005-07-10 21:06 ` James Falknor
2005-07-19 22:13 ` Andrzej Popielewicz
2005-07-20 17:21 ` Tim Newsham
2005-07-20 19:50 ` Andrzej Popielewicz
2005-07-21 7:41 ` Wesley Parish
2005-07-21 8:35 ` Andrzej Popielewicz
2005-07-21 9:27 ` Andrzej Popielewicz
2005-07-21 11:44 ` Wesley Parish
2005-07-21 17:15 ` Gunnar Ritter
[not found] ` <20050721164429.60aa8811.jrvalverde@cnb.uam.es>
2005-07-21 19:45 ` Andrzej Popielewicz [this message]
2005-07-10 21:09 ` James Falknor
2005-07-10 21:11 ` James Falknor
2005-07-10 23:28 ` M. Warner Losh
2005-07-11 3:43 ` James Falknor
2005-07-11 4:11 ` M. Warner Losh
2005-07-22 7:37 ` Peter Jeremy
2005-07-20 21:17 Brantley Coile
2005-07-20 21:18 Brantley Coile
2005-07-21 0:35 James Falknor
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=42DFFB54.80205@icpnet.pl \
--to=vasco@icpnet.pl \
/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 NNTP newsgroup(s).