Well, it's easy enough to reproduce (for me, at least). Given the file "B.scad" that contains a single line: include <BOSL2/std.scad> Given a file "untitled.scad", that contains: use <B.scad> cube( [ 3,4,5] ); OpenSCAD 2021.01 has no problems. Dev Snapshot OpenSCAD-2023.04.04 gives me the errors. I dunno. Len On Sat, Apr 8, 2023 at 8:50 PM Leonard Martin Struttmann < lenstruttmann@gmail.com> wrote: > I'm running this on a new PC that I just set up today. Can someone else > reproduce it? > > On Sat, Apr 8, 2023 at 8:42 PM Adrian Mariano <radian@cox.net> wrote: > >> Hmmm. Did something change about handling of $ variables? >> >> On Sat, Apr 08, 2023 at 08:26:55PM -0500, Leonard Martin Struttmann wrote: >> > The complete log: >> > >> > >> > Compiling design (CSG Tree generation)... >> > WARNING: Ignoring unknown variable '$attach_to' in file >> > C:/Users/red/Documents/OpenSCAD/libraries/BOSL2/attachments.scad, line >> 2320 >> > WARNING: Ignoring unknown variable '$tags_shown' in file >> > C:/Users/red/Documents/OpenSCAD/libraries/BOSL2/attachments.scad, line >> 2661 >> > WARNING: Ignoring unknown variable '$tags_shown' in file >> > C:/Users/red/Documents/OpenSCAD/libraries/BOSL2/attachments.scad, line >> 2661 >> > ERROR: Assertion '(is_list($tags_shown) || ($tags_shown == "ALL"))' >> failed >> > in file >> C:/Users/red/Documents/OpenSCAD/libraries/BOSL2/attachments.scad, >> > line 2661 >> > TRACE: called by '_is_shown' in file >> > C:/Users/red/Documents/OpenSCAD/libraries/BOSL2/attachments.scad, line >> 1848 >> > TRACE: called by 'if' in file >> > C:/Users/red/Documents/OpenSCAD/libraries/BOSL2/attachments.scad, line >> 1848 >> > TRACE: called by 'multmatrix' in file >> > C:/Users/red/Documents/OpenSCAD/libraries/BOSL2/attachments.scad, line >> 1841 >> > TRACE: call of 'attachable(anchor = [-1, -1, -1], spin = 0, orient = >> [0, 0, >> > 1], size = [3, 4, 5], size2 = undef, shift = undef, r = undef, r1 = >> undef, >> > r2 = undef, d = undef, d1 = undef, d2 = undef, l = undef, h = undef, >> vnf = >> > undef, path = undef, region = undef, extent = true, cp = [0, 0, 0], >> offset >> > = [0, 0, 0], anchors = [], two_d = false, axis = [0, 0, 1], geom = >> > ["prismoid", [3, 4, 5], [3, 4], [0, 0], [0, 0, 1], [0, 0, 0], [0, 0, 0], >> > []])' in file >> > C:/Users/red/Documents/OpenSCAD/libraries/BOSL2/attachments.scad, line >> 1819 >> > TRACE: called by 'attachable' in file >> > C:/Users/red/Documents/OpenSCAD/libraries/BOSL2/shapes3d.scad, line 60 >> > TRACE: call of 'cube(size = [3, 4, 5], center = undef, anchor = [-1, -1, >> > -1], spin = 0, orient = [0, 0, 1])' in file >> > C:/Users/red/Documents/OpenSCAD/libraries/BOSL2/shapes3d.scad, line 56 >> > TRACE: called by 'cube' in file Untitled.scad, line 3 >> > Compiling design (CSG Products generation)... >> > >> > >> > On Sat, Apr 8, 2023 at 8:24 PM Adrian Mariano <radian@cox.net> wrote: >> > >> > > I do all my development in the stable version, because that's what >> > > BOSL2 is supposed to work with, but it's working fine for me on the >> > > 3/26 dev snapshot. >> > > >> > > It looks to me like the list below doesn't show the actual error, so >> > > that makes it tough to figure out what might be wrong. Generally >> > > there should be an ERROR line first, followed by TRACE lines. >> > > >> > > On Sat, Apr 08, 2023 at 06:13:20PM -0700, Jordan Brown wrote: >> > > > Adrian and Revar, CCed, would know far better than I do whether >> there >> > > > are any known issues with BOSL2. >> > > > >> > > > Certainly the intent is that the development snapshots are >> completely >> > > > compatible. >> > > > >> > > > I don't know what the TRACE stuff is, but I don't see anything there >> > > > that says that it's an error. >> > > > >> > > > On 4/8/2023 6:04 PM, Leonard Martin Struttmann wrote: >> > > > > Here are some of the errors: >> > > > > >> > > > > TRACE: call of 'attachable(anchor = [-1, -1, -1], spin = 0, >> orient = >> > > > > [0, 0, 1], size = [3, 4, 5], size2 = undef, shift = undef, r = >> undef, >> > > > > r1 = undef, r2 = undef, d = undef, d1 = undef, d2 = undef, l = >> undef, >> > > > > h = undef, vnf = undef, path = undef, region = undef, extent = >> true, >> > > > > cp = [0, 0, 0], offset = [0, 0, 0], anchors = [], two_d = false, >> axis >> > > > > = [0, 0, 1], geom = ["prismoid", [3, 4, 5], [3, 4], [0, 0], [0, >> 0, 1], >> > > > > [0, 0, 0], [0, 0, 0], []])' in file >> > > > > C:/Users/red/Documents/OpenSCAD/libraries/BOSL2/attachments.scad, >> line >> > > > > 1819 >> > > > > TRACE: called by 'attachable' in file >> > > > > C:/Users/red/Documents/OpenSCAD/libraries/BOSL2/shapes3d.scad, >> line 60 >> > > > > TRACE: call of 'cube(size = [3, 4, 5], center = undef, anchor = >> [-1, >> > > > > -1, -1], spin = 0, orient = [0, 0, 1])' in file >> > > > > C:/Users/red/Documents/OpenSCAD/libraries/BOSL2/shapes3d.scad, >> line 56 >> > > > > TRACE: called by 'cube' in file Untitled.scad, line 3 >> > > > > >> > > > > I've narrowed it down to the Dev Snapshot not playing well with >> the >> > > > > BOSL2 library. >> > > > > >> > > > > I don't see any BOSL2 issues on github that specifically call out >> > > > > using the DEV Snapshots. >> > > > > >> > > > > Before I submit a new issue, is BOSL2 thought to work OK with Dev >> > > > > Snapshots? >> > > > > >> > > > > Thanks! >> > > > > >> > > >> >