Re: FLI type error
"Tim Bradshaw (as tfb at tfeb dot org)" <[email protected]>
| Newsgroups | gmane.lisp.lispworks.general |
|---|---|
| Message-ID | <[email protected]> |
On 7 Mar 2026, at 17:37, David McClain (as dbm at refined-audiometrics dot com) <[email protected]> wrote: > > Offhand… did the OpenGL API change since 10 years ago? Perhaps now expects an array of char, or a string pointer? I believe OpenGL has it as strict policy that every decade the entire API is deprecated, and replaced by something entirely incompatible. Shortly afterward the old API is removed altogether. Until a few years ago this was merely a scheme to keep programmers in jobs. Today it has seamlessly mutated into a scheme to keep 'AI' companies in business. The understanding is that, when the API changes, you will vibe-code a new version of your program which uses the new API. That new version will be hundreds of thousands of lines larger than the one it replaced. On close inspection it will be found to contain a bug-ridden, slow implementation of half of Common Lisp, lacking a garbage collector and whose only data type is the string. On top of that implementation will be found three things: a buggy shim which translates the old API to a the new one, an interpreter for the language the previous version was written in, and the entire source code of the old implementation. Seriously, check out the history of Xscreensaver if you doubt me. --tim [The second paragraph may be a joke. May be.] _______________________________________________ Lisp Hug - the mailing list for LispWorks users [email protected] http://www.lispworks.com/support/lisp-hug.html