Newest at the top
| 2025-11-02 23:43:20 +0100 | Nachtgespenst | (~user@user/siracusa) siracusa |
| 2025-11-02 23:34:42 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |
| 2025-11-02 23:34:34 +0100 | <monochrom> | Nice. |
| 2025-11-02 23:33:18 +0100 | <mwnaylor> | <type> **variable reminds me of the double pointers in the in the original Mac system code. Except Apple called them Ptr and Handle (I think). The Ptr held the address of allocated memory, which was stored in the Handle. This allowed blocks of memory to be moved around. Before reading/writing memory, the Handle got locked. Then unlocked when the operation was complete. |
| 2025-11-02 23:33:02 +0100 | Xe | (~Xe@perl/impostor/xe) Xe |
| 2025-11-02 23:32:43 +0100 | Xe | (~Xe@perl/impostor/xe) (Ping timeout: 256 seconds) |
| 2025-11-02 23:29:53 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-02 23:27:50 +0100 | Zemyla | (~Zemyla@72.178.108.235) Zemyla |
| 2025-11-02 23:25:46 +0100 | Inline | (~inlinE@2a02:8071:57a1:dc0:a54f:a27d:cf25:667b) (Quit: Leaving) |
| 2025-11-02 23:22:47 +0100 | Zemyla | (~Zemyla@72.178.108.235) (Ping timeout: 250 seconds) |
| 2025-11-02 23:22:13 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-11-02 23:21:33 +0100 | Anarchos | (~Anarchos@91-161-254-16.subs.proxad.net) (Quit: Vision[]: i've been blurred!) |
| 2025-11-02 23:16:15 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-02 23:13:28 +0100 | qqe | (~qqq@185.54.21.203) |
| 2025-11-02 23:09:51 +0100 | EvanR | rips the 3-star pin off monochrom's uniform |
| 2025-11-02 23:09:41 +0100 | <fgarcia> | things like " xss " have been good. less attention to the variables when the type signature and function name can be enough. haskell has been wonderful to present meaning at the desired places |
| 2025-11-02 23:08:56 +0100 | haltingsolver | (~cmo@2604:3d09:207f:8000::d1dc) (Ping timeout: 256 seconds) |
| 2025-11-02 23:08:39 +0100 | <monochrom> | OK you're right, that needs only **. I forgot where the third came from. |
| 2025-11-02 23:07:55 +0100 | <EvanR> | g:gs |
| 2025-11-02 23:07:47 +0100 | <EvanR> | f:fs |
| 2025-11-02 23:07:45 +0100 | <EvanR> | functions |
| 2025-11-02 23:07:15 +0100 | <EvanR> | c:cs |
| 2025-11-02 23:07:09 +0100 | <EvanR> | a string: cs |
| 2025-11-02 23:06:14 +0100 | <fgarcia> | for names i am not always consistent. if a function is a list of strings i am about equally as likely to use " ss " instead of " xss " |
| 2025-11-02 23:06:04 +0100 | <monochrom> | The thrid star is from passing the matrix by reference to a function. |
| 2025-11-02 23:05:44 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
| 2025-11-02 23:05:39 +0100 | <monochrom> | OK so I did row major order. For an m rows n cols matrix, I allocated a block of m pointers, then each initialized to malloc of n doubles. |
| 2025-11-02 23:04:42 +0100 | <EvanR> | where did the third star come from |
| 2025-11-02 23:04:32 +0100 | <EvanR> | an array of pointers, double** |
| 2025-11-02 23:04:17 +0100 | <EvanR> | if it was an array of double, you could pass that around using double* |
| 2025-11-02 23:03:29 +0100 | <monochrom> | It was C! What box? :) |
| 2025-11-02 23:03:17 +0100 | <EvanR> | and* |
| 2025-11-02 23:03:13 +0100 | <EvanR> | any each individual double was boxed? |
| 2025-11-02 23:01:46 +0100 | <monochrom> | Basically just because I had 2D arrays, fully dynamically allocated, and back then "double[m][n]" was not allowed for variable m,n, and I needed to pass such matrices by reference. |
| 2025-11-02 23:00:33 +0100 | <EvanR> | impressive |
| 2025-11-02 23:00:28 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-02 23:00:11 +0100 | <monochrom> | I used double*** in C a long time ago. |
| 2025-11-02 22:59:41 +0100 | <EvanR> | lol |
| 2025-11-02 22:59:29 +0100 | <darkling> | Is that what's known as a snake case variable? :) |
| 2025-11-02 22:58:55 +0100 | <EvanR> | if you find yourself using an xsss, you're now a three S haskell programmer |
| 2025-11-02 22:58:16 +0100 | <monochrom> | Yeah it's a very common convention. |
| 2025-11-02 22:57:03 +0100 | <mwnaylor> | I'd gravitated toward xss. I like getting others' opinions. |
| 2025-11-02 22:55:57 +0100 | <monochrom> | OK you already know. :) |
| 2025-11-02 22:55:39 +0100 | <monochrom> | You can use "xss" for [[a]] |
| 2025-11-02 22:54:55 +0100 | <mwnaylor> | It is an abstraction, as mapcat is a higher order function. As least for this discussion. |
| 2025-11-02 22:53:04 +0100 | jreicher | (~user@user/jreicher) jreicher |
| 2025-11-02 22:52:45 +0100 | <EvanR> | but abstract operations on any list don't get this luxury |
| 2025-11-02 22:52:30 +0100 | <EvanR> | page:pages |
| 2025-11-02 22:52:21 +0100 | <EvanR> | person:persons |
| 2025-11-02 22:52:06 +0100 | <EvanR> | if you're managing a real list of concrete things, maybe use another name |