gmane.lisp.openmcl.devel archive

351 archived articles, newest first (page 3 of 4). Latest articles →

Re: M1 port: Call for funding
Mon, 1 Jan 2024 08:50:43 -0500
Tim McNerney <[email protected]> • #11276
Re: M1 port: Call for funding
Mon, 1 Jan 2024 15:16:53 +0200
Toomas Altosaar <[email protected]> • #11275
Re: M1 port: Call for funding
Mon, 1 Jan 2024 10:37:34 +0000
Tim Bradshaw <[email protected]> • #11274
Re: M1 port: Call for funding
Sun, 31 Dec 2023 18:03:32 -0800
"R. Matthew Emerson" <[email protected]> • #11273
Re: M1 port: Call for funding
Sun, 31 Dec 2023 17:02:26 -0500
Andrew Shalit <[email protected]> • #11272
Re: M1 port: Call for funding
Sun, 31 Dec 2023 20:50:07 +0000
Tim Bradshaw <[email protected]> • #11271
Re: M1 port: Call for funding
Sun, 31 Dec 2023 15:56:18 -0500
Jon Boone <[email protected]> • #11270
Re: M1 port: Call for funding
Sun, 31 Dec 2023 12:45:17 -0800
"R. Matthew Emerson" <[email protected]> • #11269
Re: M1 port: Call for funding
Sun, 31 Dec 2023 12:35:54 -0800
Ron Garret <[email protected]> • #11268
Re: M1 port: Call for funding
Sun, 31 Dec 2023 15:05:55 -0500
Jon Boone <[email protected]> • #11267
Re: M1 port: Call for funding
Sun, 31 Dec 2023 11:38:31 -0800
Ron Garret <[email protected]> • #11266
Re: M1 port: Call for funding
Sun, 31 Dec 2023 14:23:13 -0500
Andrew Shalit <[email protected]> • #11265
Re: M1 port: Call for funding
Sun, 31 Dec 2023 14:07:47 -0500
Andrew Shalit <[email protected]> • #11264
Re: M1 port: Call for funding
Sun, 31 Dec 2023 13:59:03 -0500
Andrew Shalit <[email protected]> • #11263
Tax deductibility of contributions to the M1 port
Sun, 31 Dec 2023 10:35:26 -0800
Ron Garret <[email protected]> • #11262
Re: M1 Port - Why PPC64 rather than the Arm32 port?
Sun, 31 Dec 2023 09:32:40 -0500
Gary Palter <[email protected]> • #11261
Re: M1 Port - Why PPC64 rather than the Arm32 port?
Sun, 31 Dec 2023 09:35:59 -0500
Tim McNerney <[email protected]> • #11260
Re: M1 port: Call for funding
Sun, 31 Dec 2023 09:29:48 -0500
Gary Palter <[email protected]> • #11259
Re: M1 port: Call for funding
Sun, 31 Dec 2023 14:15:52 +0100
Joakim Sandgren <[email protected]> • #11258
M1 Port - Why PPC64 rather than the Arm32 port?
Sun, 31 Dec 2023 11:53:09 +0100
Bruce O'Neel <[email protected]> • #11257
Re: M1 port: Call for funding
Sat, 30 Dec 2023 23:43:09 -0800
"R. Matthew Emerson" <[email protected]> • #11256
Re: M1 port: Call for funding
Sat, 30 Dec 2023 22:04:43 -0800
"R. Matthew Emerson" <[email protected]> • #11255
Re: M1 port: Call for funding
Sat, 30 Dec 2023 18:56:00 -0500
Tim McNerney <[email protected]> • #11254
Re: M1 port: Call for funding
Sat, 30 Dec 2023 12:18:24 -0800
Ron Garret <[email protected]> • #11253
Re: M1 port: Call for funding
Sat, 30 Dec 2023 09:42:50 -0500
Mirko Vukovic <[email protected]> • #11252
Re: M1 port: Call for funding
Sat, 30 Dec 2023 08:42:17 -0500
Gail Zacharias <[email protected]> • #11251
Re: M1 port: Call for funding
Fri, 29 Dec 2023 12:37:24 -0800
Derrell Piper <[email protected]> • #11250
Re: M1 port: Call for funding
Fri, 29 Dec 2023 10:29:40 -0800
Ron Garret <[email protected]> • #11249
Re: M1 port: Call for funding
Fri, 29 Dec 2023 10:23:59 -0600
mikel evins <[email protected]> • #11248
Re: M1 port: Call for funding
Fri, 29 Dec 2023 09:54:28 -0500
Tim McNerney <[email protected]> • #11247
Re: M1 port: Call for funding
Fri, 29 Dec 2023 00:23:10 -0800
"R. Matthew Emerson" <[email protected]> • #11246
Re: M1 port: Call for funding
Thu, 28 Dec 2023 15:13:49 -0600
"Dan S. Camper" <[email protected]> • #11245
Re: M1 port: Call for funding
Thu, 28 Dec 2023 21:43:44 +0100
Gilbert Baumann <[email protected]> • #11244
M1 port: Call for funding
Thu, 28 Dec 2023 18:18:34 +0100
Gilbert Baumann <[email protected]> • #11243
[CfP] 17th European Lisp Symposium, May 6-7 2024, Vienna, Austria
Thu, 30 Nov 2023 16:45:28 +0100
Didier Verna <[email protected]> • #11242
Re: The M1 port and the future of CCL
Sun, 26 Nov 2023 11:01:02 -0800
"Scott L. Burson" <[email protected]> • #11241
Re: The M1 port and the future of CCL
Sun, 26 Nov 2023 10:11:28 -0600
Robert Goldman <[email protected]> • #11240
Re: The M1 port and the future of CCL
Sat, 25 Nov 2023 23:03:01 -0800
"Scott L. Burson" <[email protected]> • #11239
Re: The M1 port and the future of CCL
Sat, 25 Nov 2023 13:25:29 -0800
"R. Matthew Emerson" <[email protected]> • #11238
Re: The M1 port and the future of CCL
Sat, 25 Nov 2023 01:50:04 -0800
"R. Matthew Emerson" <[email protected]> • #11237
Re: Repetition in error message when allocating arrays with incorrect dimension(s)
Fri, 24 Nov 2023 17:07:06 -0800
"R. Matthew Emerson" <[email protected]> • #11236
Re: Smal patch for the new Debian 12.1 version of RaspberryPI OS.
Fri, 24 Nov 2023 16:44:28 -0800
"R. Matthew Emerson" <[email protected]> • #11235
Re: The M1 port and the future of CCL
Fri, 24 Nov 2023 11:33:45 -1000
J Klein <[email protected]> • #11234
Re: The M1 port and the future of CCL
Sat, 25 Nov 2023 01:37:04 +0530
Bharat Shetty <[email protected]> • #11233
Re: The M1 port and the future of CCL
Fri, 24 Nov 2023 14:30:02 -0500
Jon Boone <[email protected]> • #11232
Re: The M1 port and the future of CCL
Fri, 24 Nov 2023 18:56:19 +0000
"Mark Klein" <[email protected]> • #11231
Re: The M1 port and the future of CCL
Fri, 24 Nov 2023 14:11:00 +0100
Laughing Water <[email protected]> • #11230
Re: The M1 port and the future of CCL
Fri, 24 Nov 2023 09:58:19 +0000
peter <[email protected]> • #11229
Re: The M1 port and the future of CCL
Thu, 23 Nov 2023 13:30:00 +0000
David Ritchie <[email protected]> • #11228
Re: The M1 port and the future of CCL
Thu, 23 Nov 2023 10:28:47 +0100
Nicolas Martyanoff <[email protected]> • #11227
Re: The M1 port and the future of CCL
Wed, 22 Nov 2023 16:13:37 -0600
Robert Goldman <[email protected]> • #11226
Re: The M1 port and the future of CCL
Wed, 22 Nov 2023 14:12:44 -0800
"Scott L. Burson" <[email protected]> • #11225
Re: The M1 port and the future of CCL
Wed, 22 Nov 2023 13:37:07 -0800
Ron Garret <[email protected]> • #11224
Re: The M1 port and the future of CCL
Wed, 22 Nov 2023 21:25:15 +0000
Tim Bradshaw <[email protected]> • #11223
Re: The M1 port and the future of CCL
Wed, 22 Nov 2023 13:20:09 -0800
"Scott L. Burson" <[email protected]> • #11222
The M1 port and the future of CCL
Wed, 22 Nov 2023 11:27:15 -0800
Ron Garret <[email protected]> • #11221
Re: CCL on Sonoma
Mon, 13 Nov 2023 14:11:32 -0500
Tim McNerney <[email protected]> • #11220
CCL on Sonoma
Mon, 13 Nov 2023 10:03:30 -0800
Ron Garret <[email protected]> • #11219
Repetition in error message when allocating arrays with incorrect dimension(s)
Sat, 4 Nov 2023 23:33:33 +0100
Grégory Vanuxem <[email protected]> • #11218
Smal patch for the new Debian 12.1 version of RaspberryPI OS.
Sun, 22 Oct 2023 14:55:16 +0200
Bruce O'Neel <[email protected]> • #11217
Re: Strange Loop 2020 talk "The Economics of Programming Languages"
Fri, 13 Oct 2023 19:07:12 -0400
Jeremy Jones <[email protected]> • #11216
Re: Strange Loop 2020 talk "The Economics of Programming Languages"
Tue, 10 Oct 2023 03:58:59 -0700
"Scott L. Burson" <[email protected]> • #11215
Re: Strange Loop 2020 talk "The Economics of Programming Languages"
Mon, 09 Oct 2023 23:44:56 -0500
"Ben Hyde" <[email protected]> • #11214
Re: Strange Loop 2020 talk "The Economics of Programming Languages"
Sun, 8 Oct 2023 22:42:15 -0700
"R. Matthew Emerson" <[email protected]> • #11213
Re: Strange Loop 2020 talk "The Economics of Programming Languages"
Sun, 8 Oct 2023 11:54:02 +0000 (UTC)
Steven Nunez <[email protected]> • #11212
Strange Loop 2020 talk "The Economics of Programming Languages"
Sun, 8 Oct 2023 00:37:46 -0700
"R. Matthew Emerson" <[email protected]> • #11211
Re: how read a character without requiring a subsequent carriage return?
Tue, 29 Aug 2023 12:06:05 -0700
"R. Matthew Emerson" <[email protected]> • #11210
Re: how read a character without requiring a subsequent carriage return?
Tue, 29 Aug 2023 18:25:29 +0000
"Mark Klein" <[email protected]> • #11209
how read a character without requiring a subsequent carriage return?
Tue, 29 Aug 2023 15:49:19 +0000
"Mark Klein" <[email protected]> • #11208
Re: Clozure CL 1.12.2 release
Sun, 13 Aug 2023 15:00:08 +0100
Tim Bradshaw <[email protected]> • #11207
Re: basic GitHub action for building CCL lisp kernel?
Sun, 13 Aug 2023 05:38:03 -0500
Bryan Green <[email protected]> • #11206
Re: basic GitHub action for building CCL lisp kernel?
Sat, 12 Aug 2023 22:11:07 -0700
"R. Matthew Emerson" <[email protected]> • #11205
Re: basic GitHub action for building CCL lisp kernel?
Fri, 11 Aug 2023 10:23:00 -0700
"R. Matthew Emerson" <[email protected]> • #11204
Re: basic GitHub action for building CCL lisp kernel?
Fri, 11 Aug 2023 09:07:32 -0700
Ron Garret <[email protected]> • #11203
basic GitHub action for building CCL lisp kernel?
Thu, 10 Aug 2023 21:10:44 -0700
"R. Matthew Emerson" <[email protected]> • #11202
Re: Clozure CL 1.12.2 release
Thu, 10 Aug 2023 17:21:02 +0100
Tim Bradshaw <[email protected]> • #11201
Re: Clozure CL 1.12.2 release
Thu, 10 Aug 2023 17:20:26 +0100
Tim Bradshaw <[email protected]> • #11200
Re: Clozure CL 1.12.2 release
Thu, 10 Aug 2023 11:21:46 -0400
Gary Palter <[email protected]> • #11199
Re: Clozure CL 1.12.2 release
Thu, 10 Aug 2023 07:55:52 -0700
Ron Garret <[email protected]> • #11198
Re: Clozure CL 1.12.2 release
Thu, 10 Aug 2023 13:10:20 +0100
Tim Bradshaw <[email protected]> • #11197
Re: Clozure CL 1.12.2 release
Thu, 10 Aug 2023 00:29:22 -0700
Ron Garret <[email protected]> • #11196
Re: Clozure CL 1.12.2 release
Thu, 10 Aug 2023 03:19:49 -0400
Gary Palter <[email protected]> • #11195
Re: Clozure CL 1.12.2 release
Thu, 10 Aug 2023 08:46:13 +0200
James Anderson <[email protected]> • #11194
Re: Clozure CL 1.12.2 release
Wed, 9 Aug 2023 17:14:01 -0600
Laughing Water <[email protected]> • #11193
Re: Clozure CL 1.12.2 release
Wed, 9 Aug 2023 14:45:32 +0200
[email protected] • #11192
Clozure CL 1.12.2 release
Tue, 8 Aug 2023 22:43:36 -0700
"R. Matthew Emerson" <[email protected]> • #11191
Re: Intel APX
Tue, 25 Jul 2023 09:05:08 +0530
Bharat Shetty <[email protected]> • #11190
Intel APX
Mon, 24 Jul 2023 14:40:00 -0700
"R. Matthew Emerson" <[email protected]> • #11189
new release
Sat, 15 Jul 2023 13:43:34 -0700
"R. Matthew Emerson" <[email protected]> • #11188
Re: Where is the source of LET* macro
Thu, 25 May 2023 20:04:19 +0300
Adlai C <[email protected]> • #11187
Re: Where is the source of LET* macro
Tue, 23 May 2023 18:11:16 -0400
Robert Munyer <[email protected]> • #11186
Re: multiple read-time conditionals, puzzlement
Tue, 23 May 2023 18:06:21 -0400
Robert Munyer <[email protected]> • #11185
Re: RPi arm failures in locking and threading
Tue, 23 May 2023 18:00:31 -0400
Robert Munyer <[email protected]> • #11184
Re: CCL on Big Sur and Apple M1 chips
Tue, 23 May 2023 17:57:20 -0400
Robert Munyer <[email protected]> • #11183
Re: Obfuscated Lisp contest anyone? (Seriously)
Sun, 7 May 2023 09:30:24 -0700
Ron Garret <[email protected]> • #11182
Re: Obfuscated Lisp contest anyone? (Seriously)
Sun, 7 May 2023 16:58:02 +0300
Tim McNerney <[email protected]> • #11181
Re: Obfuscated Lisp contest anyone? (Seriously)
Sun, 7 May 2023 11:01:55 +0300
Adlai C <[email protected]> • #11180
Re: Where is the source of LET* macro
Fri, 21 Apr 2023 13:02:59 +0100
Tim Bradshaw <[email protected]> • #11179
Re: Where is the source of LET* macro
Tue, 18 Apr 2023 15:13:51 -0400
Mirko Vukovic <[email protected]> • #11178
Re: Obfuscated Lisp contest anyone? (Seriously)
Sat, 15 Apr 2023 22:54:40 +0200
Michał "phoe" Herda <[email protected]> • #11177
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.