From: Sebastien F4GRX <f4grx@f4grx.net>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Software written in B
Date: Thu, 15 Jun 2023 10:33:53 +0200 [thread overview]
Message-ID: <21361f2d-eda9-fd68-09f0-ded89b16285b@f4grx.net> (raw)
In-Reply-To: <ZIrJ9eSIfKxKwy/H@indra.papnet.eu>
Hello again,
OK for the absence of escapes. It's not a big deal.
And thank you for the authorization. I will surely follow your progress.
There is a typo in your goto.b decompilation, an AND operator is missing
before testing for end of string, here is a patch:
diff --git a/examples/squoze_goto.b b/examples/squoze_goto.b
index bb39e66..8d48bb3 100644
--- a/examples/squoze_goto.b
+++ b/examples/squoze_goto.b
@@ -31,7 +31,7 @@ l:
goto l;
}
while ((ch=getchar())==' ');
- while (ch!=' ' & ch!='*n' ch!='*0') {
+ while (ch!=' ' & ch!='*n' & ch!='*0') {
lchar(s, i++, ch);
ch = getchar();
}
Sebastien
Le 15/06/2023 à 10:21, Angelo Papenhoff a écrit :
> On 15/06/23, Sebastien F4GRX wrote:
>> I see that su.b contains non-ascii characters ($11,$12,$13,$14) which
>> tripped my linux console when I attempted a copy paste, since $13 is
>> XOFF :) Is there a way to escape these characters? Or update them, since
>> it looks like a password provided on command line.
> The last1120 C compiler does not have an escape mechanism for strings,
> so it's highly unlikely the B compiler had it.
>
>> May I have your authorization for copying these files into my own b
>> compiler repository ( https://git.sr.ht/~f4grx/bpars )? What licence and
>> attribution info shall I indicate?
> Sure, sure. I reversed goto.b today and am currently working on if.b. So
> just keep an eye on the files.
>
> best,
> Angelo
next prev parent reply other threads:[~2023-06-15 8:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 10:14 [TUHS] " Sebastien F4GRX
2023-06-07 10:38 ` [TUHS] " Lars Brinkhoff
2023-06-07 15:05 ` Angelo Papenhoff
2023-06-07 15:57 ` Clem Cole
2023-06-07 16:21 ` Lars Brinkhoff
2023-06-07 17:26 ` Bakul Shah
2023-06-07 18:16 ` Phil Budne
2023-06-07 23:49 ` Andrew Hume
2023-06-08 2:10 ` segaloco via TUHS
2023-06-08 3:31 ` Phil Budne
2023-06-08 15:05 ` segaloco via TUHS
2023-06-14 11:51 ` Angelo Papenhoff
2023-06-14 20:03 ` Angelo Papenhoff
2023-06-14 21:53 ` segaloco via TUHS
2023-06-14 22:05 ` Angelo Papenhoff
2023-06-15 8:00 ` Sebastien F4GRX
2023-06-15 8:21 ` Angelo Papenhoff
2023-06-15 8:33 ` Sebastien F4GRX [this message]
2023-06-17 8:19 ` Angelo Papenhoff
2023-06-19 9:52 ` Sebastien F4GRX
2023-06-19 10:18 ` Sebastien F4GRX
2023-06-19 10:48 ` Lars Brinkhoff
2023-06-19 10:55 ` G. Branden Robinson
2023-06-19 11:07 ` Sebastien F4GRX
2023-06-19 18:44 ` segaloco via TUHS
2023-06-23 10:59 ` Angelo Papenhoff
2023-06-23 13:32 ` Sebastien F4GRX
2023-06-23 14:01 ` Angelo Papenhoff
2023-06-23 14:14 ` Sebastien F4GRX
2023-06-23 14:39 ` Angelo Papenhoff
2023-06-23 14:10 ` Sebastien F4GRX
2023-06-23 14:49 ` Angelo Papenhoff
2023-06-23 15:31 ` Sebastien F4GRX
2023-06-23 15:36 ` Angelo Papenhoff
2023-06-23 15:53 ` Sebastien F4GRX
2023-06-08 14:41 ` arnold
2023-06-09 8:56 ` Sebastien F4GRX
2023-06-09 9:57 ` Lars Brinkhoff
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=21361f2d-eda9-fd68-09f0-ded89b16285b@f4grx.net \
--to=f4grx@f4grx.net \
--cc=tuhs@tuhs.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 NNTP newsgroup(s).