Dear Dave,
Yes, I remember this problem. It's because I used bytevec_key as an
identifier in popvision before it became a global identifier in Pop-11;
later it was introduced into the language and that broke popvision.
I worked out a solution some years ago, but the version of popvision
with the fix in it has got lost somehow. I think my solution was similar
to yours (though may have also involved a conditional test). I'll have
another look at it, but I think you can safely carry on with the
modification you've made.
I'm not sure how to install a new version of popvision - I'm aware that
there are various Poplog trees now and that there's been discussion of
which one is canonical, but I can't remember the conclusion - I guess I
should look back through popforum to find out.
Best wishes,
David
On 26/06/2021 14:59, [email protected] wrote:
Dear Forum members,
I am very interest in Poplog and used it a lot back in the early 80’s
for computer vision related problems.
I have recently decided to “scrape the rust of my Poplog knowledge” and
get stuck-in once more.
I am trying to build Popvision on my 64 bit machine running Linux mint
V19 with Poplog V16.
I can compile as directed for 64 bit - so far so good, but when I use
mkpopvision to build the package I get the following mishap:-
./mkpopvision > out.txt
;;; MISHAP - idw: ILLEGAL DECLARATION OF WORD (missing ; after vars?)
;;; INVOLVING: bytevec_key
;;; FILE :
/home/david/Documents/Poplog/poplog_base/pop/packages/lib/../p
;;; opvision/lib/newbytearray.p LINE NUMBER: 16
;;; PRINT DOING
;;; DOING : ident_declare defclass section loadlib do_load
uses_lib_idents
;;; section loadlib do_load uses_lib_idents section loadlib
do_load
;;; uses_lib_idents loadlib do_load uses_lib_idents section
loadlib
;;; do_load uses_lib_idents section loadlib do_load
uses_lib_idents
;;; section loadfile mkimage section
I have found a solution which appears to solve the problem, though I am
not sure if the problem really exists in the popvision package
or within pop11, thoughts please.
My solution is to change the name of the “bytevec” class defined in file
“newbytearray.p” to “bytevect” this also impacts the following two files
within the popvision package:
“array_random.p” and “arraylooup.p”.
This solution appears to work – I am continuing to test the package but
currently believe that all is well.
any thoughts, advice, or help will be much appreciated.
I am a new member of the Forum so Hello to you all.
Best regards
Dave
