Parsing behavior change v4 -> v5?

[ekipan]

\ file "bug"
marker ----
: h: ( u-u) hex  dup 0 do  parse-name
  evaluate c, loop  decimal ;
create rels 8
h: 00 01 02 03  02 12 22 32  \ iiii
h: 00 01 02 03  02 12 22 32  \
h: 03 11 12 13  01 02 12 22 \    jjj
h: 01 02 03 11  02 12 22 23 \   .  j
drop

\ durexforth v4
include bug
ok
rels dump
39c1 00 01 02 03 02 12 22 32 ......"2
39c9 00 01 02 03 02 12 22 32 ......"2
39d1 03 11 12 13 01 02 12 22 ......."
39d9 01 02 03 11 02 12 22 23 ......"#
39e1 33 33 45 31 20 55 08 20 20e1 u.
( ... )
ok
( working as expected in v4 )

durexForth v5.0.0.0
include bug
jjj?
rels dump
3965 00 01 02 03 02 12 22 32 ......"2
396d 03 11 12 13 01 02 12 22 ......."
3975 20 12 40 39 20 76 19 20  .@9 V.
( ... )
ok
( parse-name behaving strangely? )

I thought maybe it was the lone end-of-line backslash but deleting it didn't fix the problem.

[ekipan]

Gforth's result for reference.

[ekipan]

When I loaded the code into v and pressed f7 it seemed to work correctly even in v5. If you cannot reproduce then perhaps this is once again a problem with the "Host file system" drive feature I'm using in VICE.

[ekipan]

I loaded from "Host file system" using v bug, attached a new disk image, saved :w!bug, disabled hfs, power cycled, then include bug worked as expected. I don't understand why it works in v4 but not v5.

[jkotlinski]

I guess its time for the old ”git bisect” :-) tis 17 dec. 2024 kl. 18:34 skrev ekipan ***@***.***>:

…

I loaded from "Host file system" using v bug, attached a new disk image, saved :w!bug, disabled hfs, power cycled, then include bug worked as expected. I don't understand why it works in v4 but not v5. — Reply to this email directly, view it on GitHub <#584 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAY34O6PMJJINAXM243YCVD2GBOCXAVCNFSM6AAAAABTYT27RWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBZGEZDQNJUGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[jkotlinski]

It seemed to work for me with v5, but maybe I don't use same settings as you?

I find VICE settings mysterious and I do not trust all settings.

I use VICE 3.6.0 locally.

Do you know if there is a particular durexForth revision when this stopped working for you?

[jkotlinski]

To anyone it may concern, I would welcome help in solving problems like these. I feel it is a bit beyond me.