Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #172151 > unrolled thread
| Started by | Bart <bc@freeuk.com> |
|---|---|
| First post | 2023-08-13 14:53 +0100 |
| Last post | 2023-08-29 04:43 -0700 |
| Articles | 20 on this page of 306 — 31 participants |
Back to article view | Back to comp.lang.c
Build Systems Bart <bc@freeuk.com> - 2023-08-13 14:53 +0100
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-13 21:45 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-13 23:43 +0100
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-14 01:16 +0100
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-14 00:46 +0000
Re: Build Systems gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-14 01:05 +0000
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-13 18:59 -0700
Dev on Windoze (Was: Build Systems) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-14 02:44 +0000
Re: Dev on Windoze (Was: Build Systems) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-13 20:53 -0700
Re: Dev on Windoze (Was: Build Systems) Matthew Ernisse <matt@going-flying.com> - 2023-08-17 22:00 +0000
Re: Dev on Windoze (Was: Build Systems) Michael S <already5chosen@yahoo.com> - 2023-08-18 03:51 -0700
Re: Dev on Windoze (Was: Build Systems) bart c <bart4858@gmail.com> - 2023-08-18 04:58 -0700
Re: Dev on Windoze (Was: Build Systems) Matthew Ernisse <matt@going-flying.com> - 2023-08-18 13:02 +0000
Re: Dev on Windoze Phil Carmody <pc+usenet@asdf.org> - 2023-08-20 16:14 +0300
Re: Dev on Windoze "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-20 11:05 -0700
Re: Dev on Windoze (Was: Build Systems) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-18 16:16 -0700
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-14 04:03 +0000
Re: Build Systems gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-14 10:14 +0000
Re: Build Systems Karl Meyer <karlmeyer25@gmail.com> - 2023-08-14 05:16 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-14 10:35 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-14 15:06 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-14 14:58 +0100
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-14 15:49 +0000
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-14 18:00 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-15 11:00 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-15 11:40 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-15 15:21 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-15 16:11 +0100
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-15 15:39 +0000
Re: Build Systems MJ OS_EXAMINE <m6502x64@gmail.com> - 2023-08-15 08:58 -0700
Re: Build Systems gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-15 16:44 +0000
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-15 20:00 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-15 18:03 +0200
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-15 17:01 +0000
Re: Build Systems gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-15 17:07 +0000
Re: Build Systems Phil Carmody <pc+usenet@asdf.org> - 2023-08-15 23:17 +0300
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-15 22:57 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-15 18:49 +0100
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-15 13:13 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-15 23:09 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-15 23:36 +0100
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-15 15:55 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-16 01:05 +0100
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-16 01:39 +0000
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-16 11:37 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-16 12:15 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-16 15:16 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-16 16:34 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-16 18:07 +0100
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-16 17:43 +0000
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-16 18:51 +0100
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-16 21:26 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-16 22:25 +0100
Re: Build Systems Richard Harnden <richard.nospam@gmail.com> - 2023-08-17 00:15 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-17 01:02 +0100
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-17 02:56 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-17 11:21 +0100
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-17 21:26 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-17 23:40 +0100
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-19 00:43 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-17 15:45 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-18 00:24 +0100
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-17 17:46 -0700
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-17 18:29 -0700
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-17 19:13 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-18 14:55 +0200
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-18 14:34 -0700
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-18 14:34 -0700
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-18 15:19 -0700
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-18 15:43 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-19 13:19 +0200
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-26 20:56 -0700
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-26 20:57 -0700
Re: Build Systems "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-08-27 00:01 -0700
Re: Build Systems candycane@f172.n1.z21.fsxnet (candycane) - 2023-08-27 03:34 +1300
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-27 08:32 +0000
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-27 16:58 +0200
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-27 11:58 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-27 16:52 +0200
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-27 11:59 -0700
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-18 01:49 +0000
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-18 02:19 -0700
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-19 01:21 +0100
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-18 18:36 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-19 13:51 +0200
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-19 05:35 -0700
Re: Build Systems Kelsey Bjarnason <kbjarnason@gmail.com> - 2023-08-19 00:35 -0700
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-19 09:54 -0700
Re: Build Systems Kelsey Bjarnason <kbjarnason@gmail.com> - 2023-08-19 12:30 -0700
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-19 13:44 -0700
Re: Build Systems Kelsey Bjarnason <kbjarnason@gmail.com> - 2023-08-21 17:58 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-22 02:28 +0100
Re: Build Systems Kelsey Bjarnason <kbjarnason@gmail.com> - 2023-08-22 00:12 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-22 11:13 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-22 11:36 +0100
Re: Build Systems Richard Harnden <richard.nospam@gmail.com> - 2023-08-22 13:37 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-22 13:51 +0100
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-22 14:51 +0000
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-22 17:19 +0100
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-22 09:30 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-22 17:51 +0100
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-22 16:36 +0000
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-22 16:50 +0000
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-22 18:06 +0100
Re: Build Systems kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-22 20:46 +0000
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-22 12:47 -0700
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-26 21:06 -0700
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-22 17:04 +0000
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-20 00:10 +0100
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-19 17:50 -0700
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-20 20:48 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-20 22:07 +0100
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-21 00:51 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-21 01:26 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-21 02:02 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-21 02:07 +0100
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-21 03:13 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-21 11:09 +0100
Re: Build Systems Richard Harnden <richard.nospam@gmail.com> - 2023-08-21 13:12 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-21 14:12 +0100
Re: Build Systems Richard Harnden <richard.nospam@gmail.com> - 2023-08-21 14:47 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-21 19:06 +0100
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-21 18:40 +0000
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-21 14:39 -0700
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-21 12:23 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-21 21:55 +0100
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-22 01:31 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-22 02:18 +0100
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-22 14:41 +0000
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-22 08:03 -0700
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-22 15:33 +0000
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-22 16:20 +0100
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-22 15:40 +0000
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-22 17:03 +0100
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-23 03:18 +0100
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-22 19:51 -0700
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-25 02:23 +0100
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-24 21:24 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-25 11:31 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-25 10:53 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-25 13:55 +0200
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-25 13:54 +0000
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-25 20:55 +0100
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-25 20:49 -0700
Re: Build Systems Richard Harnden <richard.nospam@gmail.com> - 2023-08-23 08:42 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-23 11:37 +0100
Re: Build Systems Anton Shepelev <anton.txt@g{oogle}mail.com> - 2023-08-23 14:02 +0300
Re: Build Systems Richard Harnden <richard.nospam@gmail.com> - 2023-08-23 15:02 +0100
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-25 02:17 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-23 14:28 +0100
Re: Build Systems Anton Shepelev <anton.txt@g{oogle}mail.com> - 2023-08-23 19:54 +0300
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-23 19:33 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-23 21:13 +0100
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-23 23:09 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-24 15:32 +0200
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-24 15:51 +0000
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-24 18:58 +0100
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-24 18:29 +0000
Re: Build Systems vallor <vallor@cultnix.org> - 2023-08-24 20:41 +0000
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-24 23:08 +0000
Re: Build Systems Rainer Weikusat <rweikusat@talktalk.net> - 2023-08-25 17:22 +0100
Re: Build Systems Spiros Bousbouras <spibou@gmail.com> - 2023-08-25 16:39 +0000
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-25 16:54 +0000
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-25 17:02 +0000
Re: Build Systems Rainer Weikusat <rweikusat@talktalk.net> - 2023-08-25 19:21 +0100
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-25 18:56 +0000
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-24 11:44 -0700
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-24 18:47 +0000
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-24 21:20 +0100
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-24 22:59 +0000
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-25 02:18 +0100
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-24 20:17 -0700
Re: Build Systems Anton Shepelev <anton.txt@g{oogle}mail.com> - 2023-08-24 16:30 +0300
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-23 17:43 +0000
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-23 20:15 +0100
Re: Build Systems Anton Shepelev <anton.txt@gmail.moc> - 2023-08-26 18:19 +0300
Re: Build Systems Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-26 21:47 -0700
Re: Build Systems Anton Shepelev <anton.txt@g{oogle}mail.com> - 2023-08-28 11:31 +0300
Re: Build Systems Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-28 06:48 -0700
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-25 02:11 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-25 11:27 +0100
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-25 13:52 +0000
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-25 15:40 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-25 20:04 +0200
Re: Build Systems candycane@f172.n1.z21.fsxnet (candycane) - 2023-08-26 00:47 +1300
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-25 21:26 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-26 01:42 +0100
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-27 01:16 +0100
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-25 05:51 +0000
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-24 23:17 -0700
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-21 02:52 +0000
Re: Build Systems vallor <vallor@cultnix.org> - 2023-08-21 03:02 +0000
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-21 06:05 +0000
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-21 11:32 +0100
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-19 14:42 +0000
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-19 08:09 -0700
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-19 15:59 +0000
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-19 09:38 -0700
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-19 18:16 +0000
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-19 21:02 +0000
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-19 14:13 -0700
Re: Build Systems Ike Naar <ike@sdf.org> - 2023-08-19 19:10 +0000
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-19 21:00 +0000
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-19 14:22 -0700
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-19 17:56 -0700
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-19 18:13 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-20 14:13 +0200
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-20 06:05 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-20 16:15 +0200
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-20 09:25 -0700
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-20 13:35 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-21 14:43 +0200
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-21 05:52 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-21 14:30 +0100
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-21 15:18 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-21 23:26 +0100
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-21 16:11 -0700
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-21 14:47 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-21 23:20 +0100
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-21 15:45 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-22 00:57 +0100
Re: Build Systems vallor <vallor@cultnix.org> - 2023-08-20 14:24 +0000
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-20 09:09 -0700
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-20 17:28 +0000
Re: Build Systems Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-19 20:26 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-18 14:50 +0200
Re: Build Systems Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-08-18 13:19 +0000
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-17 17:16 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-17 17:24 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-18 15:32 +0200
Re: Build Systems Michael S <already5chosen@yahoo.com> - 2023-08-18 07:22 -0700
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-18 07:48 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-18 17:11 +0200
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-18 08:58 -0700
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-18 16:32 -0700
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-20 04:02 -0700
Re: Build Systems "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-22 12:26 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-19 13:56 +0200
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-19 05:43 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-16 11:23 +0200
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-16 02:34 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-16 12:52 +0200
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-16 03:56 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-16 13:23 +0200
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-16 12:55 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-17 15:52 +0200
Re: Build Systems Michael S <already5chosen@yahoo.com> - 2023-08-17 02:14 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-17 15:56 +0200
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-17 16:01 +0000
Re: Build Systems Michael S <already5chosen@yahoo.com> - 2023-08-17 09:07 -0700
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-17 16:20 +0000
Re: Build Systems Michael S <already5chosen@yahoo.com> - 2023-08-17 09:31 -0700
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-17 17:24 +0000
Re: Build Systems Phil Carmody <pc+usenet@asdf.org> - 2023-08-19 14:06 +0300
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-19 04:39 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-19 16:46 +0200
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-19 16:00 +0000
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-20 14:15 +0200
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-20 07:25 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-20 18:03 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-17 19:51 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-18 16:44 +0200
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-18 08:21 -0700
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-18 15:39 +0000
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-18 17:47 +0200
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-18 10:49 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-19 15:16 +0200
Re: Build Systems bart c <bart4858@gmail.com> - 2023-08-19 07:58 -0700
Re: Build Systems Öö Tiib <ootiib@hot.ee> - 2023-08-19 09:05 -0700
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-15 12:48 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-15 21:36 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-15 21:43 +0100
Re: Build Systems Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-15 14:07 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-16 12:46 +0200
Really? (Was: Build Systems) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-15 13:15 +0000
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-15 09:54 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-15 11:07 +0100
Re: Build Systems Öö Tiib <ootiib@hot.ee> - 2023-08-15 03:42 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-15 12:14 +0100
Re: Build Systems Öö Tiib <ootiib@hot.ee> - 2023-08-15 05:53 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-15 15:57 +0100
Re: Build Systems Öö Tiib <ootiib@hot.ee> - 2023-08-15 09:10 -0700
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-14 14:49 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-14 14:39 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-15 11:08 +0200
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-15 02:56 -0700
Re: Build Systems Öö Tiib <ootiib@hot.ee> - 2023-08-15 03:23 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-15 11:45 +0100
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-15 03:53 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-15 13:15 +0100
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-15 06:22 -0700
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-16 01:20 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-16 12:57 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-16 12:19 +0100
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-16 15:18 +0200
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-16 18:12 +0100
Re: Build Systems Bart <bc@freeuk.com> - 2023-08-16 18:18 +0100
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-16 17:45 +0000
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-15 15:30 +0200
Re: Build Systems Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-15 06:58 -0700
Re: Build Systems Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-15 14:06 +0000
Re: Build Systems David Brown <david.brown@hesbynett.no> - 2023-08-15 17:08 +0200
Re: Build Systems Vir Campestris <vir.campestris@invalid.invalid> - 2023-08-15 21:46 +0100
Re: Build Systems scott@slp53.sl.home (Scott Lurndal) - 2023-08-14 15:48 +0000
Re: Build Systems Thiago Adams <thiago.adams@gmail.com> - 2023-08-15 12:16 -0700
Re: Build Systems Michael S <already5chosen@yahoo.com> - 2023-08-29 04:43 -0700
Page 13 of 16 — ← Prev page 1 … 11 12 [13] 14 15 16 Next page →
| From | Malcolm McLean <malcolm.arthur.mclean@gmail.com> |
|---|---|
| Date | 2023-08-16 02:34 -0700 |
| Message-ID | <7fb8d5b6-4172-4bf8-a3e9-858d02b5e193n@googlegroups.com> |
| In reply to | #172356 |
On Wednesday, 16 August 2023 at 10:23:40 UTC+1, David Brown wrote: > > And when people want to install software to use on Windows or Linux, how > many want to compile the software from source in order to use the > software (as distinct from modify it or copy parts of it)? I'd guess > that for Linux, the figure is less than 0.1% of users - and for Windows, > 0.01% or fewer. Virtually everyone wanting Lua on Windows will download > a binary installer. Virtually everyone wanting Lua on Linux will use > their package manager - "yum install lua", "apt-get install lua", or > whatever gui they like for their particular distribution. Even people > using source-based Linux distributions like Gentoo will not see that the > source code is downloaded and compiled on their system. > > Building projects from source code is not always easy, and often does > not have detailed information about requirements, because it is not > something many people do, and those who do it, are usually experienced > developers. Github source code is for developers, not users, and it is > expected that people are seriously interested in the project and willing > to spend time reading documentation and learning about it. People go to > the lua github page because they are interested in lua development - > maybe adding extensions, or reporting issues, or looking at integrating > it as a scripting language in their own code. The contributors to the > github site are interested in enhancing and improving the lua compiler, > interpreter, runtime and libraries - they are not going to waste their > time writing idiot's guide to compiling on Windows. And they are not > interested in people who want to build the software just so that they > can say it compiled - they are interested in people who want to /use/ > the software. > My understanding of Lua is that, whilst it can be used as a standalone language, it's really meant for adding scripting to applications. If you're writing the game level editor then of course the programmer works closely with the users, and it's acceptable to have the level editor call a binary executable. But if you want scripting in the game itself then you have to include the Lua source code. S yes, users rather than developers of Lua itself have to be able to incorporate it into a project and compile it easily.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2023-08-16 12:52 +0200 |
| Message-ID | <ubi9pf$394g8$2@dont-email.me> |
| In reply to | #172357 |
On 16/08/2023 11:34, Malcolm McLean wrote: > On Wednesday, 16 August 2023 at 10:23:40 UTC+1, David Brown wrote: >> >> And when people want to install software to use on Windows or Linux, how >> many want to compile the software from source in order to use the >> software (as distinct from modify it or copy parts of it)? I'd guess >> that for Linux, the figure is less than 0.1% of users - and for Windows, >> 0.01% or fewer. Virtually everyone wanting Lua on Windows will download >> a binary installer. Virtually everyone wanting Lua on Linux will use >> their package manager - "yum install lua", "apt-get install lua", or >> whatever gui they like for their particular distribution. Even people >> using source-based Linux distributions like Gentoo will not see that the >> source code is downloaded and compiled on their system. >> >> Building projects from source code is not always easy, and often does >> not have detailed information about requirements, because it is not >> something many people do, and those who do it, are usually experienced >> developers. Github source code is for developers, not users, and it is >> expected that people are seriously interested in the project and willing >> to spend time reading documentation and learning about it. People go to >> the lua github page because they are interested in lua development - >> maybe adding extensions, or reporting issues, or looking at integrating >> it as a scripting language in their own code. The contributors to the >> github site are interested in enhancing and improving the lua compiler, >> interpreter, runtime and libraries - they are not going to waste their >> time writing idiot's guide to compiling on Windows. And they are not >> interested in people who want to build the software just so that they >> can say it compiled - they are interested in people who want to /use/ >> the software. >> > My understanding of Lua is that, whilst it can be used as a standalone > language, it's really meant for adding scripting to applications. Certainly embedding it within other applications is a major purpose of the language, yes. It is becoming more mature as a stand-alone language, with more libraries, but it is very popular for adding to other programs. As you say, Lua is a common choice for scripting in games. I used it myself as a scripting language in an embedded program, many moons ago. > If you're > writing the game level editor then of course the programmer works > closely with the users, and it's acceptable to have the level editor > call a binary executable. But if you want scripting in the game itself then > you have to include the Lua source code. > > S yes, users rather than developers of Lua itself have to be able to > incorporate it into a project and compile it easily. > Sure. But if you want to do that, you read the relevant sections of the manual and see which files you need, which options you want, what configuration you want, and how you should combine it with your own code. You need to know how to integrate Lua with your code - how your application will start the Lua runtime or call Lua code, how the Lua code will call /your/ functions (in C or whatever), how to wrap your functions, variables, classes, etc., into Lua tables and functions. There is a lot involved here - it's not a "download and compile" task. But then, you wouldn't be doing this unless you actually wanted to use Lua in your program and are willing to invest the effort to do so.
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.arthur.mclean@gmail.com> |
|---|---|
| Date | 2023-08-16 03:56 -0700 |
| Message-ID | <84cdb234-a021-414c-b0eb-4dc6c3898153n@googlegroups.com> |
| In reply to | #172362 |
On Wednesday, 16 August 2023 at 11:52:46 UTC+1, David Brown wrote: > On 16/08/2023 11:34, Malcolm McLean wrote: > > On Wednesday, 16 August 2023 at 10:23:40 UTC+1, David Brown wrote: > >> > >> And when people want to install software to use on Windows or Linux, how > >> many want to compile the software from source in order to use the > >> software (as distinct from modify it or copy parts of it)? I'd guess > >> that for Linux, the figure is less than 0.1% of users - and for Windows, > >> 0.01% or fewer. Virtually everyone wanting Lua on Windows will download > >> a binary installer. Virtually everyone wanting Lua on Linux will use > >> their package manager - "yum install lua", "apt-get install lua", or > >> whatever gui they like for their particular distribution. Even people > >> using source-based Linux distributions like Gentoo will not see that the > >> source code is downloaded and compiled on their system. > >> > >> Building projects from source code is not always easy, and often does > >> not have detailed information about requirements, because it is not > >> something many people do, and those who do it, are usually experienced > >> developers. Github source code is for developers, not users, and it is > >> expected that people are seriously interested in the project and willing > >> to spend time reading documentation and learning about it. People go to > >> the lua github page because they are interested in lua development - > >> maybe adding extensions, or reporting issues, or looking at integrating > >> it as a scripting language in their own code. The contributors to the > >> github site are interested in enhancing and improving the lua compiler, > >> interpreter, runtime and libraries - they are not going to waste their > >> time writing idiot's guide to compiling on Windows. And they are not > >> interested in people who want to build the software just so that they > >> can say it compiled - they are interested in people who want to /use/ > >> the software. > >> > > My understanding of Lua is that, whilst it can be used as a standalone > > language, it's really meant for adding scripting to applications. > Certainly embedding it within other applications is a major purpose of > the language, yes. It is becoming more mature as a stand-alone > language, with more libraries, but it is very popular for adding to > other programs. As you say, Lua is a common choice for scripting in > games. I used it myself as a scripting language in an embedded program, > many moons ago. > > If you're > > writing the game level editor then of course the programmer works > > closely with the users, and it's acceptable to have the level editor > > call a binary executable. But if you want scripting in the game itself then > > you have to include the Lua source code. > > > > S yes, users rather than developers of Lua itself have to be able to > > incorporate it into a project and compile it easily. > > > Sure. But if you want to do that, you read the relevant sections of the > manual and see which files you need, which options you want, what > configuration you want, and how you should combine it with your own > code. You need to know how to integrate Lua with your code - how your > application will start the Lua runtime or call Lua code, how the Lua > code will call /your/ functions (in C or whatever), how to wrap your > functions, variables, classes, etc., into Lua tables and functions. > There is a lot involved here - it's not a "download and compile" task. > But then, you wouldn't be doing this unless you actually wanted to use > Lua in your program and are willing to invest the effort to do so. > I wonder if it's the answer for the problem of how to specify the output format of pixels in the Baby X resource compiler?. It's a very heavy-weight solution. But it would provide the necessary flexibility.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2023-08-16 13:23 +0200 |
| Message-ID | <ubibj8$394g8$6@dont-email.me> |
| In reply to | #172363 |
On 16/08/2023 12:56, Malcolm McLean wrote: > On Wednesday, 16 August 2023 at 11:52:46 UTC+1, David Brown wrote: >> Sure. But if you want to do that, you read the relevant sections of the >> manual and see which files you need, which options you want, what >> configuration you want, and how you should combine it with your own >> code. You need to know how to integrate Lua with your code - how your >> application will start the Lua runtime or call Lua code, how the Lua >> code will call /your/ functions (in C or whatever), how to wrap your >> functions, variables, classes, etc., into Lua tables and functions. >> There is a lot involved here - it's not a "download and compile" task. >> But then, you wouldn't be doing this unless you actually wanted to use >> Lua in your program and are willing to invest the effort to do so. >> > I wonder if it's the answer for the problem of how to specify the output > format of pixels in the Baby X resource compiler?. It's a very heavy-weight > solution. But it would provide the necessary flexibility. > If you are looking at Lua, then you could go a lot further than that. For one thing, you could write the whole resource compiler in Lua - it would be simpler and shorter than doing it in C. There are XML parsing libraries in Lua. You could also use Lua as the format for your configuration files, rather than XML. I have often used Python as the configuration format for Python programs I have written - then reading the configuration is just an "import", without any need to make parsers. (Of course, you have to be able to trust the users and the configuration file writers in such cases.) This is particularly handy if you want loops or other calculated configuration - if a resource configuration file is supposed to include "image000.png" up to "image999.png", it's a lot easier in Lua than doing a thousand copy-paste-edit operations in an XML file!
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2023-08-16 12:55 -0700 |
| Message-ID | <87il9elq2q.fsf@nosuchdomain.example.com> |
| In reply to | #172362 |
David Brown <david.brown@hesbynett.no> writes:
[...]
> Sure. But if you want to do that, you read the relevant sections of
> the manual and see which files you need, which options you want, what
> configuration you want, and how you should combine it with your own
> code. You need to know how to integrate Lua with your code - how your
> application will start the Lua runtime or call Lua code, how the Lua
> code will call /your/ functions (in C or whatever), how to wrap your
> functions, variables, classes, etc., into Lua tables and
> functions. There is a lot involved here - it's not a "download and
> compile" task. But then, you wouldn't be doing this unless you
> actually wanted to use Lua in your program and are willing to invest
> the effort to do so.
And none of that requires building Lua from source.
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2023-08-17 15:52 +0200 |
| Message-ID | <ubl8n6$3prfv$2@dont-email.me> |
| In reply to | #172405 |
On 16/08/2023 21:55, Keith Thompson wrote: > David Brown <david.brown@hesbynett.no> writes: > [...] >> Sure. But if you want to do that, you read the relevant sections of >> the manual and see which files you need, which options you want, what >> configuration you want, and how you should combine it with your own >> code. You need to know how to integrate Lua with your code - how your >> application will start the Lua runtime or call Lua code, how the Lua >> code will call /your/ functions (in C or whatever), how to wrap your >> functions, variables, classes, etc., into Lua tables and >> functions. There is a lot involved here - it's not a "download and >> compile" task. But then, you wouldn't be doing this unless you >> actually wanted to use Lua in your program and are willing to invest >> the effort to do so. > > And none of that requires building Lua from source. > It might do. But it won't use the plain build instructions. For some uses, you can probably use a prebuilt lua runtime library. In other cases, you /do/ want to build the source - but you are not building the normal "lua" and "luac" programs. You are building object files as part of your main application, with whatever configuration you want for the lua parts. For example, lua normally uses 64-bit integers as its only integer type, while in an 32-bit embedded system you might prefer to use 32-bit integers in your embedded lua. And of course you'd be using a cross-compiler, not a host compiler.
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2023-08-17 02:14 -0700 |
| Message-ID | <d0fbf07d-f1b5-4aa8-ac8e-a954addb6358n@googlegroups.com> |
| In reply to | #172362 |
On Wednesday, August 16, 2023 at 1:52:46 PM UTC+3, David Brown wrote: > Certainly embedding it within other applications is a major purpose of > the language, yes. It is becoming more mature as a stand-alone > language, with more libraries, but it is very popular for adding to > other programs. As you say, Lua is a common choice for scripting in > games. I used it myself as a scripting language in an embedded program, > many moons ago. Did it work? I mean, not an easy technical part of embedding an interpreter. Did the "human" part work? Did people that were supposed to write scripts bothered to learn the language and to start writing?
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2023-08-17 15:56 +0200 |
| Message-ID | <ubl8tt$3prfv$3@dont-email.me> |
| In reply to | #172438 |
On 17/08/2023 11:14, Michael S wrote: > On Wednesday, August 16, 2023 at 1:52:46 PM UTC+3, David Brown wrote: >> Certainly embedding it within other applications is a major purpose of >> the language, yes. It is becoming more mature as a stand-alone >> language, with more libraries, but it is very popular for adding to >> other programs. As you say, Lua is a common choice for scripting in >> games. I used it myself as a scripting language in an embedded program, >> many moons ago. > > Did it work? > I mean, not an easy technical part of embedding an interpreter. > Did the "human" part work? Did people that were supposed to write > scripts bothered to learn the language and to start writing? > Yes, at least for some simple cases. But those people were just me in that particular case - I used Lua as a convenient way to write hardware test scripts for the system. I haven't actually made much use of it since, and that project was cancelled (nothing to do with lua or any of the electronics or software - the mechanics were too expensive). However, it is definitely something I would use again if I felt that something more than a very simple command-line interface were useful in an embedded project, and the hardware was big enough to support the overhead (something like 60-70 KB code, IIRC).
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2023-08-17 16:01 +0000 |
| Message-ID | <zvrDM.215514$uLJb.196259@fx41.iad> |
| In reply to | #172438 |
Michael S <already5chosen@yahoo.com> writes: >On Wednesday, August 16, 2023 at 1:52:46=E2=80=AFPM UTC+3, David Brown wrot= >e: >> Certainly embedding it within other applications is a major purpose of=20 >> the language, yes. It is becoming more mature as a stand-alone=20 >> language, with more libraries, but it is very popular for adding to=20 >> other programs. As you say, Lua is a common choice for scripting in=20 >> games. I used it myself as a scripting language in an embedded program,= >=20 >> many moons ago. > >Did it work? >I mean, not an easy technical part of embedding an interpreter. >Did the "human" part work? Did people that were supposed to write >scripts bothered to learn the language and to start writing? We also have some stand-alone[*] software that runs on our CPUs that uses an embedded lua interpreter. Users have had no problems with it at all. [*] in this context, bare-metal sans OS.
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2023-08-17 09:07 -0700 |
| Message-ID | <93fc5974-415b-4dcd-8304-cd2eb292b42bn@googlegroups.com> |
| In reply to | #172466 |
On Thursday, August 17, 2023 at 7:01:51 PM UTC+3, Scott Lurndal wrote: > Michael S <already...@yahoo.com> writes: > >On Wednesday, August 16, 2023 at 1:52:46=E2=80=AFPM UTC+3, David Brown wrot= > >e: > >> Certainly embedding it within other applications is a major purpose of=20 > >> the language, yes. It is becoming more mature as a stand-alone=20 > >> language, with more libraries, but it is very popular for adding to=20 > >> other programs. As you say, Lua is a common choice for scripting in=20 > >> games. I used it myself as a scripting language in an embedded program,= > >=20 > >> many moons ago. > > > >Did it work? > >I mean, not an easy technical part of embedding an interpreter. > >Did the "human" part work? Did people that were supposed to write > >scripts bothered to learn the language and to start writing? > We also have some stand-alone[*] software that runs on our CPUs > that uses an embedded lua interpreter. Users have had no problems > with it at all. > > [*] in this context, bare-metal sans OS. Who are users in this case?
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2023-08-17 16:20 +0000 |
| Message-ID | <ANrDM.215515$uLJb.142133@fx41.iad> |
| In reply to | #172467 |
Michael S <already5chosen@yahoo.com> writes: >On Thursday, August 17, 2023 at 7:01:51=E2=80=AFPM UTC+3, Scott Lurndal wro= >te: >> Michael S <already...@yahoo.com> writes:=20 >> >On Wednesday, August 16, 2023 at 1:52:46=3DE2=3D80=3DAFPM UTC+3, David B= >rown wrot=3D=20 >> >e:=20 >> >> Certainly embedding it within other applications is a major purpose of= >=3D20=20 >> >> the language, yes. It is becoming more mature as a stand-alone=3D20=20 >> >> language, with more libraries, but it is very popular for adding to=3D= >20=20 >> >> other programs. As you say, Lua is a common choice for scripting in=3D= >20=20 >> >> games. I used it myself as a scripting language in an embedded program= >,=3D=20 >> >=3D20 >> >> many moons ago.=20 >> >=20 >> >Did it work?=20 >> >I mean, not an easy technical part of embedding an interpreter.=20 >> >Did the "human" part work? Did people that were supposed to write=20 >> >scripts bothered to learn the language and to start writing? >> We also have some stand-alone[*] software that runs on our CPUs=20 >> that uses an embedded lua interpreter. Users have had no problems=20 >> with it at all.=20 >>=20 >> [*] in this context, bare-metal sans OS. > >Who are users in this case? Firmware engineers, customer field support engineers and in some cases, customers.
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2023-08-17 09:31 -0700 |
| Message-ID | <9be6a67f-4747-44dc-a99d-cea238d4acc8n@googlegroups.com> |
| In reply to | #172469 |
On Thursday, August 17, 2023 at 7:21:02 PM UTC+3, Scott Lurndal wrote: > Michael S <already...@yahoo.com> writes: > >On Thursday, August 17, 2023 at 7:01:51=E2=80=AFPM UTC+3, Scott Lurndal wro= > >te: > >> Michael S <already...@yahoo.com> writes:=20 > >> >On Wednesday, August 16, 2023 at 1:52:46=3DE2=3D80=3DAFPM UTC+3, David B= > >rown wrot=3D=20 > >> >e:=20 > >> >> Certainly embedding it within other applications is a major purpose of= > >=3D20=20 > >> >> the language, yes. It is becoming more mature as a stand-alone=3D20=20 > >> >> language, with more libraries, but it is very popular for adding to=3D= > >20=20 > >> >> other programs. As you say, Lua is a common choice for scripting in=3D= > >20=20 > >> >> games. I used it myself as a scripting language in an embedded program= > >,=3D=20 > >> >=3D20 > >> >> many moons ago.=20 > >> >=20 > >> >Did it work?=20 > >> >I mean, not an easy technical part of embedding an interpreter.=20 > >> >Did the "human" part work? Did people that were supposed to write=20 > >> >scripts bothered to learn the language and to start writing? > >> We also have some stand-alone[*] software that runs on our CPUs=20 > >> that uses an embedded lua interpreter. Users have had no problems=20 > >> with it at all.=20 > >>=20 > >> [*] in this context, bare-metal sans OS. > > > >Who are users in this case? > Firmware engineers, customer field support engineers and in some > cases, customers. I would think that in your case "customers" are also software or electronic engineers, mostly developers of Telecom/datacom equipment. Still your people are less lazy and more willing to learn than 80% of my co-workers. Field support engineers that even contemplate an idea of writing scripts by themselves are especially startling.
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2023-08-17 17:24 +0000 |
| Message-ID | <nJsDM.558160$SuUf.418415@fx14.iad> |
| In reply to | #172471 |
Michael S <already5chosen@yahoo.com> writes: >On Thursday, August 17, 2023 at 7:21:02=E2=80=AFPM UTC+3, Scott Lurndal wro= >te: >> Michael S <already...@yahoo.com> writes:=20 >> >On Thursday, August 17, 2023 at 7:01:51=3DE2=3D80=3DAFPM UTC+3, Scott Lu= >rndal wro=3D=20 >> >te:=20 >> >> Michael S <already...@yahoo.com> writes:=3D20=20 >> >> >On Wednesday, August 16, 2023 at 1:52:46=3D3DE2=3D3D80=3D3DAFPM UTC+3= >, David B=3D=20 >> >rown wrot=3D3D=3D20=20 >> >> >e:=3D20 >> >> >> Certainly embedding it within other applications is a major purpose= > of=3D >> >=3D3D20=3D20=20 >> >> >> the language, yes. It is becoming more mature as a stand-alone=3D3D= >20=3D20=20 >> >> >> language, with more libraries, but it is very popular for adding to= >=3D3D=3D=20 >> >20=3D20=20 >> >> >> other programs. As you say, Lua is a common choice for scripting in= >=3D3D=3D=20 >> >20=3D20=20 >> >> >> games. I used it myself as a scripting language in an embedded prog= >ram=3D=20 >> >,=3D3D=3D20=20 >> >> >=3D3D20=20 >> >> >> many moons ago.=3D20=20 >> >> >=3D20=20 >> >> >Did it work?=3D20=20 >> >> >I mean, not an easy technical part of embedding an interpreter.=3D20= >=20 >> >> >Did the "human" part work? Did people that were supposed to write=3D2= >0 >> >> >scripts bothered to learn the language and to start writing? >> >> We also have some stand-alone[*] software that runs on our CPUs=3D20= >=20 >> >> that uses an embedded lua interpreter. Users have had no problems=3D20= >=20 >> >> with it at all.=3D20=20 >> >>=3D20 >> >> [*] in this context, bare-metal sans OS.=20 >> >=20 >> >Who are users in this case? >> Firmware engineers, customer field support engineers and in some=20 >> cases, customers. > >I would think that in your case "customers" are also software or electronic >engineers, mostly developers of Telecom/datacom equipment. > >Still your people are less lazy and more willing to learn than 80% of my >co-workers. Field support engineers that even contemplate an idea of >writing scripts by themselves are especially startling. We have really good FEs, that's a fact.
[toc] | [prev] | [next] | [standalone]
| From | Phil Carmody <pc+usenet@asdf.org> |
|---|---|
| Date | 2023-08-19 14:06 +0300 |
| Message-ID | <87sf8f9tq8.fsf@fatphil.org> |
| In reply to | #172466 |
scott@slp53.sl.home (Scott Lurndal) writes: > Michael S <already5chosen@yahoo.com> writes: >>On Wednesday, August 16, 2023 at 1:52:46=E2=80=AFPM UTC+3, David Brown wrot= >>e: >>> Certainly embedding it within other applications is a major purpose of=20 >>> the language, yes. It is becoming more mature as a stand-alone=20 >>> language, with more libraries, but it is very popular for adding to=20 >>> other programs. As you say, Lua is a common choice for scripting in=20 >>> games. I used it myself as a scripting language in an embedded program,= >>=20 >>> many moons ago. >> >>Did it work? >>I mean, not an easy technical part of embedding an interpreter. >>Did the "human" part work? Did people that were supposed to write >>scripts bothered to learn the language and to start writing? > > We also have some stand-alone[*] software that runs on our CPUs > that uses an embedded lua interpreter. Users have had no problems > with it at all. > > [*] in this context, bare-metal sans OS. The crypto subsystems on a bunch of ARM SoCs from multiple vendors (TI & Freescale at least) are written in Lua too, and have been for well over a decade. Phil -- We are no longer hunters and nomads. No longer awed and frightened, as we have gained some understanding of the world in which we live. As such, we can cast aside childish remnants from the dawn of our civilization. -- NotSanguine on SoylentNews, after Eugen Weber in /The Western Tradition/
[toc] | [prev] | [next] | [standalone]
| From | bart c <bart4858@gmail.com> |
|---|---|
| Date | 2023-08-19 04:39 -0700 |
| Message-ID | <cd21da1c-859b-4b22-90c6-87cf19ab250bn@googlegroups.com> |
| In reply to | #172522 |
On Saturday, 19 August 2023 at 12:22:42 UTC+1, Phil Carmody wrote: > sc...@slp53.sl.home (Scott Lurndal) writes: > > Michael S <already...@yahoo.com> writes: > >>On Wednesday, August 16, 2023 at 1:52:46=E2=80=AFPM UTC+3, David Brown wrot= > >>e: > >>> Certainly embedding it within other applications is a major purpose of=20 > >>> the language, yes. It is becoming more mature as a stand-alone=20 > >>> language, with more libraries, but it is very popular for adding to=20 > >>> other programs. As you say, Lua is a common choice for scripting in=20 > >>> games. I used it myself as a scripting language in an embedded program,= > >>=20 > >>> many moons ago. > >> > >>Did it work? > >>I mean, not an easy technical part of embedding an interpreter. > >>Did the "human" part work? Did people that were supposed to write > >>scripts bothered to learn the language and to start writing? > > > > We also have some stand-alone[*] software that runs on our CPUs > > that uses an embedded lua interpreter. Users have had no problems > > with it at all. > > > > [*] in this context, bare-metal sans OS. > > The crypto subsystems on a bunch of ARM SoCs from multiple vendors (TI & > Freescale at least) are written in Lua too, and have been for well over > a decade. That's interesting. One of the limitations of Lua was that it didn't have proper integer type, it used a 64-bit float. Integer values could only be represented exactly up to 2**52 or so. However recent versions of Lua (not LuaJIT) have acquired a proper 64-bit integer type; presumably it was needed. That was well within the last decade. (LuaJIT does not have it.)
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2023-08-19 16:46 +0200 |
| Message-ID | <ubqkkv$sjb3$1@dont-email.me> |
| In reply to | #172524 |
On 19/08/2023 13:39, bart c wrote: > That's interesting. One of the limitations of Lua was that it didn't have proper integer type, it used a 64-bit float. > Lua is configurable, and can support different types. When I embedded in a 32-bit microcontroller program, I use 32-bit integers as the number type.
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <864-117-4973@kylheku.com> |
|---|---|
| Date | 2023-08-19 16:00 +0000 |
| Message-ID | <20230819085912.518@kylheku.com> |
| In reply to | #172536 |
On 2023-08-19, David Brown <david.brown@hesbynett.no> wrote: > On 19/08/2023 13:39, bart c wrote: >> That's interesting. One of the limitations of Lua was that it didn't have proper integer type, it used a 64-bit float. >> > > Lua is configurable, and can support different types. When I embedded > in a 32-bit microcontroller program, I use 32-bit integers as the number > type. I don't feel the party has properly started until someone makes that sort of thing a command line option. Or better yet, environment variable. -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2023-08-20 14:15 +0200 |
| Message-ID | <ubt057$1bhkn$3@dont-email.me> |
| In reply to | #172544 |
On 19/08/2023 18:00, Kaz Kylheku wrote: > On 2023-08-19, David Brown <david.brown@hesbynett.no> wrote: >> On 19/08/2023 13:39, bart c wrote: >>> That's interesting. One of the limitations of Lua was that it didn't have proper integer type, it used a 64-bit float. >>> >> >> Lua is configurable, and can support different types. When I embedded >> in a 32-bit microcontroller program, I use 32-bit integers as the number >> type. > > I don't feel the party has properly started until someone makes that > sort of thing a command line option. Or better yet, environment > variable. > I don't think something like that would be remotely helpful for Lua, but that is possibly due to my lack of experience with the language. You'd get a more complete answer from a Lua newsgroup.
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.arthur.mclean@gmail.com> |
|---|---|
| Date | 2023-08-20 07:25 -0700 |
| Message-ID | <7a8ae21e-b73b-491e-9e05-58db050cec00n@googlegroups.com> |
| In reply to | #172574 |
On Sunday, 20 August 2023 at 13:15:49 UTC+1, David Brown wrote: > On 19/08/2023 18:00, Kaz Kylheku wrote: > > On 2023-08-19, David Brown <david...@hesbynett.no> wrote: > >> On 19/08/2023 13:39, bart c wrote: > >>> That's interesting. One of the limitations of Lua was that it didn't have proper integer type, it used a 64-bit float. > >>> > >> > >> Lua is configurable, and can support different types. When I embedded > >> in a 32-bit microcontroller program, I use 32-bit integers as the number > >> type. > > > > I don't feel the party has properly started until someone makes that > > sort of thing a command line option. Or better yet, environment > > variable. > > > I don't think something like that would be remotely helpful for Lua, but > that is possibly due to my lack of experience with the language. You'd > get a more complete answer from a Lua newsgroup. > Seems unexceptional to me. You might need the full range of 64 bit integers for some reason. But most likely all the integers in the program are under 2^53 and fractions are useful. So a default to using 64-bit floats and an option to use 64-bit integers would be the obvious thing to provide, if Lua is indeed configurable.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2023-08-20 18:03 +0200 |
| Message-ID | <ubtdfp$1e4oo$1@dont-email.me> |
| In reply to | #172582 |
On 20/08/2023 16:25, Malcolm McLean wrote: > On Sunday, 20 August 2023 at 13:15:49 UTC+1, David Brown wrote: >> On 19/08/2023 18:00, Kaz Kylheku wrote: >>> On 2023-08-19, David Brown <david...@hesbynett.no> wrote: >>>> On 19/08/2023 13:39, bart c wrote: >>>>> That's interesting. One of the limitations of Lua was that it didn't have proper integer type, it used a 64-bit float. >>>>> >>>> >>>> Lua is configurable, and can support different types. When I embedded >>>> in a 32-bit microcontroller program, I use 32-bit integers as the number >>>> type. >>> >>> I don't feel the party has properly started until someone makes that >>> sort of thing a command line option. Or better yet, environment >>> variable. >>> >> I don't think something like that would be remotely helpful for Lua, but >> that is possibly due to my lack of experience with the language. You'd >> get a more complete answer from a Lua newsgroup. >> > Seems unexceptional to me. You might need the full range of 64 bit integers > for some reason. But most likely all the integers in the program are under 2^53 > and fractions are useful. So a default to using 64-bit floats and an option to > use 64-bit integers would be the obvious thing to provide, if Lua is indeed > configurable. It is indeed configurable (though it was a long time ago when I used it much). You configure it for the type of numbers you want to use, then build it - it is compile-time configuration, not run-time configuration. The point of using smaller types (such as 32-bit int) is to make it more efficient on smaller targets (such as small embedded systems). It would be of questionable benefit to have it a choice of 64-bit or 32-bit integers at runtime (remember, Lua is byte encoded and runs on a virtual machine) - I'd imagine that would be very much slower than simply fixing on 64-bit would be.
[toc] | [prev] | [next] | [standalone]
Page 13 of 16 — ← Prev page 1 … 11 12 [13] 14 15 16 Next page →
Back to top | Article view | comp.lang.c
csiph-web