Search
Friday, 29th of May 2020, 22:03:58 UTC
22:56:09
Lord_of_Life_
** NICK Lord_of_Life
0:47:15
White_Flame
$FACET_OF_TIME_CUBE
0:54:57
edgar-rft
is it time to load some bytes?
0:59:50
edgar-rft
(time (ldb <bytespec> <integer>)) => morning
1:20:47
seok
is there a library to draw charts?
1:21:42
Josh_2
there are wrappers for gnuplot
3:17:17
beach
Good morning everyone!
3:28:44
seok
how do I check if a variable is a string?
3:28:55
seok
(equal (type-of x) ??)
3:29:20
seok
'(simple-array character) neither
3:51:57
beach
seok: You mean if THE VALUE OF A VARIABLE is a string?
3:53:09
beach
seok: In general, if you don't have a predicate like STRINGP, the way to check it is (TYPEP <object> '<type-descriptor>) so in this case (TYPEP X 'STRING).
4:01:27
edgar-rft
AFAIK a string string can be made variable by using a fill-pointer
4:01:42
edgar-rft
* one string too many
4:02:06
ffwacom
can I (use-package :blah) but assign :blah to an alias?
4:02:42
ffwacom
the main issue is the package :iterate and :generators both define the #'next symbol
4:02:45
ffwacom
this is in common lisp
4:02:51
beach
What does it mean to assign a keyword to an alias?
4:03:13
beach
You should avoid :USEing packages other than the CL package.
4:03:30
ffwacom
how should I approach it?
4:03:37
beach
Use explicit package prefixes.
4:03:59
beach
And if the name of the package is too long, use package-local nicknames, now available in every significant implementation.
4:05:10
beach
By using explicit package prefixes, your code is easier to understand, because the person reading it can immediately see what package a symbol comes from.
4:06:39
ffwacom
that sounds fine, I'd really like the package names shorter
4:07:16
beach
You can make it a single letter if you want, using package-local nicknames.
4:08:22
beach
... so that i:next is the symbol in iterators, and g:next is the one from generators.
4:11:43
ffwacom
beach: That worked a treat, thanks
4:44:42
White_Flame
ffwacom: there's package-local-nicknames, which is an extension that pretty much every lisp implementationhas now
4:45:03
beach
I think that's what I said. No?
4:45:15
White_Flame
oh, right at the end, yeah
4:45:27
White_Flame
ACTION skimmed too fast
6:40:47
no-defun-allowed
Hello phoe.
7:00:46
__jrjsmrtn__
** NICK _jrjsmrtn
7:36:31
liberliver1
** NICK liberliver
8:07:26
beach
Do we have a collective name for the type specifier names AND, OR, EQL, MEMBER, MOD, NOT, SATISFIES, and VALUES.
8:08:35
beach
They are the ones that are not names of any types.
8:13:13
specbot
Type Specifiers: http://www.lispworks.com/reference/HyperSpec/Body/04_bc.htm
8:13:28
phoe
compound-only type specifiers
8:14:07
beach
I guess I can live with that.
9:25:26
MrtnDk[m]
<beach "I guess I can live with that."> How?
9:26:05
no-defun-allowed
Quite easily, that's the phrase used in the Common Lisp Hyperspec.
9:26:06
beach
I'll just put "compound-only" in the name of the file in which I planned to put code for those type specifier names.
9:27:22
beach
MrtnDk[m]: Are you new here? I don't recognize your nick.
9:27:44
MrtnDk[m]
beach: I think so, yes.
9:28:00
beach
Great! What brings you to #lisp?
9:28:13
phoe
MrtnDk[m]: helloooo, welcome to #lisp
9:32:21
MrtnDk[m]
phoe: Thank you! 🙂
9:37:06
phoe
if we can help you in anything related to Common Lisp, just post it here
Saturday, 30th of May 2020, 10:03:58 UTC