20:06:04dloweanyway, I don't like to say no, so I'm still mulling it over. I really hate to have both :min and :minute to an API, and I also am not going to break other people just so the API can be more consistent
1:01:32fiddlerwoaroof_Anyways, I just discovered that the #p macro has a high chance of ruining your day.
1:03:03fiddlerwoaroof_I built a little GUI app in Lispworks for some AWS stuff and when I shared it with my coworkers, it didn’t work for them. This lead me to discover that it’s evaluated to a pathname object at read tome
1:03:41fiddlerwoaroof_So that ~ is expanded to the home directory on the build machine and not the end-user’s home directory.
1:03:56Xachfiddlerwoaroof_: that depends on the implementation
1:04:15Xach~ is not standard - user-homedir-pathname is the standard thing
1:04:23Xachfiddlerwoaroof_: but that's an interesting failure mode!
1:14:01no-defun-allowedYou would have to dolist at compile or read-time.
1:14:16aethvms14: I mean, sure, that looks like it works, but I personally would rather have a series of write-foos than "<~a~~{~~{~~^ ~~a=\"~~a\"~~}~~}>~~a</~a>"
1:14:42no-defun-allowedSomething like (macrolet ((generator-list (&rest list) (cons 'progn (loop for name in list collect (list 'generator name))))) (generator-list p main section article))
1:14:45aethvms14: Also keep in mind that when you're generating format strings you basically commit to writing a macro since it's much more efficient for FORMAT to know what its format strings are ahead of time because FORMAT can be very optimized
1:14:46vms14aeth: the only complaint I have with this format is I know there is no need to repeat arg arg
1:14:57vms14how was to make format use the last argument?
5:24:42MichaelRaskinI guess most of the print-object methods defined use the standard printer for the objects' components. So consistency (or coverage) might be rather hard to achieve
5:25:23MichaelRaskinAlthough I don't know if there are any inconsistencies in the standard printer across implementations
5:26:30beachWhy does the fact that the "standard printer" is used make it hard to achieve consistency?
5:29:28MichaelRaskinOK, what should be achieved compared to the standart print-object generic function?
5:30:52beachNothing. Just the possibility of a common library rather than a separate one for each Common Lisp implementation.
5:31:32beachI am always trying to cut down on the combined maintenance burden for free Common Lisp implementations.
5:34:59beachThese things come up when I need some module for SICL that does not seem very implementation specific to me, but I also don't see an existing library.
5:36:58beachSo, why does the fact that the "standard printer" is used make it hard to achieve consistency?
5:37:26MichaelRaskinNo, with such a motivation it doesn't create any problems