Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #232111 > unrolled thread

Looking for ~Dartmouth BASIC

Back to article view | Back to linux.debian.user

Contents

  Looking for ~Dartmouth BASIC Richard Owlett <rowlett@cloud85.net> - 2021-02-25 20:40 +0100
    Re: Looking for ~Dartmouth BASIC Dan Ritter <dsr@randomstring.org> - 2021-02-25 21:00 +0100
      Re: Looking for ~Dartmouth BASIC Doug McGarrett <dmcgarrett@optonline.net> - 2021-02-26 00:20 +0100
        Re: Looking for ~Dartmouth BASIC ghe2001 <ghe2001@protonmail.com> - 2021-02-26 00:40 +0100
          Re: Looking for ~Dartmouth BASIC Jude DaShiell <jdashiel@panix.com> - 2021-02-26 02:20 +0100
        Re: Looking for ~Dartmouth BASIC Dan Ritter <dsr@randomstring.org> - 2021-02-26 01:00 +0100
    Re: Looking for ~Dartmouth BASIC Joe <joe@jretrading.com> - 2021-02-25 23:20 +0100

#232111 — Looking for ~Dartmouth BASIC

I was trained on CORC/CUPL
   Can you say I/O == "026/line printer"
I want to prototype a problem.
What BASIC in Debian repository most resembles "Dartmouth BASIC"?

[toc] | [next] | [standalone]

#232113

Richard Owlett wrote: 
> I was trained on CORC/CUPL
>   Can you say I/O == "026/line printer"
> I want to prototype a problem.
> What BASIC in Debian repository most resembles "Dartmouth BASIC"?


Your choices are yabasic and python3-pcbasic. Both of them try
to be something like Microsoft BASIC.

I would strongly recommend learning Python. If you haven't
touched BASIC in the last few years, you won't be any faster
figuring out a new BASIC than you will learning Python, and
there's a far larger community of Python users.

-dsr-

[toc] | [prev] | [next] | [standalone]

#232126

On 2/25/21 2:56 PM, Dan Ritter wrote:
> Richard Owlett wrote:
>> I was trained on CORC/CUPL
>>    Can you say I/O == "026/line printer"
>> I want to prototype a problem.
>> What BASIC in Debian repository most resembles "Dartmouth BASIC"?
>
> Your choices are yabasic and python3-pcbasic. Both of them try
> to be something like Microsoft BASIC.
>
> I would strongly recommend learning Python. If you haven't
> touched BASIC in the last few years, you won't be any faster
> figuring out a new BASIC than you will learning Python, and
> there's a far larger community of Python users.
>
> -dsr-
>
Whatever BASIC you wind up with make SURE it has a CASE statement.
Original BASICs did not--that includes Microsoft BASIC and George
Washington BASIC. I'm told that at least some modern versions do
have the CASE statement. About 30 years ago, I was asked by my
boss to write a program for him that had a lot of possibilities to be
addressed. He wanted it in BASIC, since he was familiar with that
language. Three pages later, it was done. I could have done it in less
than a page with Turbo PASCAL, because that language, as just about
all modern languages, does have a CASE statement. (So does BASH.)
PS--I'm not a programmer, I'm an RF Engineer, retired.
--doug

[toc] | [prev] | [next] | [standalone]

#232127

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

There's a Java program claiming to be a Dartmouth BASIC:

https://github.com/emesx/jBasic

--
Glenn English
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJgODO+ACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDIE0AgAqxETxz6Gk0xixfuiTWyLedpLCG4Jz4aSN9v/inXBu93OkarI
Hr93YOLBANn9JbYf034O6MQ+Z/rcEIYqdDQON5mgBR3w8VKtyJ+s1V6+HVJ5
6JwaQo47lMf+y/P9oa5flXMhZYS6+bJeYkjipjR0vuwxvlFAWCjHgzA4oCo1
32uBAokVDxYsLX2ExXy/0geLuccjCKpN7Rr2amPqmdt1gXsExKpJ/VUVj9Ho
CU9mwzdliDTZg/SgtuZT+WyAdJYaS2CelCmzliVCLiFRh/+GtINzFrOG9Nrb
3CMEYRj5dKGYyhSdAsPqisAgWQdmHfIAhHOlSbw5Rv9FJWIshOoteA==
=ceId
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#232132

yabasic has the case statement.

[toc] | [prev] | [next] | [standalone]

#232128

Doug McGarrett wrote: 
> 
> PS--I'm not a programmer, I'm an RF Engineer, retired.



The essence of the UNIX philosophy is not "make small utilities that
can be fit together with pipes" but to assume that at any moment,
a user might decide to be a programmer or a sysadmin and should have
the tools to do that.

The problems of UNIX generally come from assuming either that
users are never devs and sysadmins, or that all users are devs
and sysadmins.

-dsr-

[toc] | [prev] | [next] | [standalone]

#232119

On Thu, 25 Feb 2021 13:33:57 -0600
Richard Owlett <rowlett@cloud85.net> wrote:

> I was trained on CORC/CUPL
>    Can you say I/O == "026/line printer"
> I want to prototype a problem.

Depends what type of problem. For many numerical problems, a
spreadsheet is a good prototyping language. In fact I still have a
spreadsheet for making certain types of PCB component footprints, it
does the job well enough that it wasn't worth doing it again
'properly'. I used a spreadsheet for calculating ModeLines for X, back
when they were necessary and a certain very common monitor resolution
wasn't available ready-made.

For a standalone database RAD tool, MS Access is unbeatable, though not
free or even cheap.


> What BASIC in Debian repository most resembles "Dartmouth BASIC"?
>

Why are you choosing Dartmouth BASIC as your target? After 'learning'
BASIC on Applesoft on an AppleII, which I suspect resembles the first
BASIC, I was overjoyed to find BBC Basic on an Acorn machine. Orders of
magnitude better. When I learned (non-object) Pascal, I wondered what
the fuss was about, it wasn't greatly removed from BBC Basic. Would
your problem benefit from recursion? If so, the earliest BASICs are
probably of little use. But of course it is easy to ignore the more
advanced bits of any BASIC, and just use the primitive parts.

And so on.... you're learning, so learn the software tool most
appropriate to your problem. I always picked an application that would
be of actual use to me when learning another language, language
tutorials tend to choose easy examples (who really has a use for the
Towers of Hanoi?), and avoid the real-world tricky bits. You find the
tricky bits quite quickly when you try to write a program that does
something useful.

For example, as far as I could tell, it is impossible to write a
completely 'legal' duplex serial driver in Python, though the subtleties
of it escape me now, and I was able to bodge something that worked. It
was something of the order of two objects down near hardware level that
each needed to be created before the other, or something similar. But
there was a slightly iffy way around it.

-- 
Joe

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web