miskatonic has quit [Quit: ERC (IRC client for Emacs 24.5.1)]
f8l has quit [Ping timeout: 245 seconds]
_whitelogger has joined #picolisp
ubLIX has quit [Quit: ubLIX]
_whitelogger has joined #picolisp
_whitelogger has joined #picolisp
orivej has quit [Ping timeout: 268 seconds]
aw- has quit [Quit: Leaving.]
aw- has joined #picolisp
f8l has joined #picolisp
aw- has quit [Quit: Leaving.]
alexshendi has joined #picolisp
alexshendi has quit [Read error: Connection reset by peer]
beneroth has joined #picolisp
<beneroth>
hi all
<Regenaxer>
Hi beneroth!
aw- has joined #picolisp
<beneroth>
Hi Regenaxer !
<beneroth>
Hi aw- !
<aw->
hi
<Regenaxer>
Hello aw-!
aw- has quit [Quit: Leaving.]
aw- has joined #picolisp
aw-1 has joined #picolisp
aw-1 has quit [Client Quit]
aw- has quit [Ping timeout: 246 seconds]
_whitelogger has joined #picolisp
<beneroth>
Regenaxer, how to make a folded +Key? (+Fold +Key +String) ?
<Regenaxer>
Yes, but I never tried that :)
<beneroth>
ok, I do now :)
<Regenaxer>
Might be that there is an assumption somewhere that the key matches exactly
<beneroth>
I will find out :)
<Regenaxer>
ok :)
<Regenaxer>
'collect' etc. handle +Key directly iirc
<Regenaxer>
What I did sometimes is use +Uppc
<Regenaxer>
but thats on the input level (GUI)
<Regenaxer>
so internally the key is always direct
<Regenaxer>
+Lowc would be an alternative
<Regenaxer>
But there is no +Fold on the input side here
<beneroth>
I see
<beneroth>
yeah, so alternative would be to have two properties, label (+String) and id (+Key +String) folded
<Regenaxer>
Hmm, I would not keep duplicate data
<Regenaxer>
I often had "Matchcodes" as +Key
<Regenaxer>
They were upper case both internally and in GUI
<Regenaxer>
That's more clear
<Regenaxer>
"Folded" means "tolerant", not exact
<Regenaxer>
so not suitable for +Key in my feeling
<beneroth>
hm.. you're right
<Regenaxer>
But I understand your point too
<beneroth>
anyway, (+Fold +Key) does not work, no folding happening, the +Fold gets ignored :)
<Regenaxer>
Makes sense
<beneroth>
T
<Regenaxer>
uh, I suspected so
<beneroth>
I have to handle weird special chars in item names :)
<Regenaxer>
and you need to preserve them?
<beneroth>
as display names, yeah
<Regenaxer>
Then for search too
<Regenaxer>
just plain +Key?
<Regenaxer>
So in fact what you have is what is matchcode in my cases
<beneroth>
kinda
<Regenaxer>
I did store both too
<beneroth>
using two properties then?
<Regenaxer>
eg "Japanese Yen" currency with key "JPY"
<Regenaxer>
yes
<beneroth>
T
<beneroth>
currency is a classical case for such codes
<Regenaxer>
All currencies are this way, but globally defined
<Regenaxer>
The keys are standard I mean
<Regenaxer>
You can simply use +Fold +Ref
<Regenaxer>
and check uniqueness
<Regenaxer>
eg a local relation class
<beneroth>
T
<Regenaxer>
it is a little waste of space though
<Regenaxer>
(unless you *want* to allow non-uniqueness)
<beneroth>
I think I go for two properties in this use case here
<Regenaxer>
ek
<Regenaxer>
ok
<beneroth>
display name and key code
<Regenaxer>
yeah
<Regenaxer>
Makes the situation clear to the user
<beneroth>
omg no my test for +Fold +Key was useless. I made a stupid mistake.
<beneroth>
retesting
<Regenaxer>
:)
<beneroth>
aye!
<Regenaxer>
On the DB it works probably, but some utilities might shortcut if they see +Key
<beneroth>
+Fold +Key DOES WORK
<beneroth>
T
<beneroth>
I will test and check source
<Regenaxer>
Good to know
<beneroth>
but it correctly produces a folded +Key index
<Regenaxer>
cool
<beneroth>
(I looked at the index tree)
<Regenaxer>
collect and pilog are candidates
<Regenaxer>
yes, tree should be fine
<beneroth>
(db) needs explicit call/passing of (fold)ed value
<Regenaxer>
yes, I think so too
<beneroth>
same with (collect)
<Regenaxer>
ok, but this can be handled
<Regenaxer>
good to know
<beneroth>
aye. still better then two properties, right?
<Regenaxer>
yes
ubLIX has joined #picolisp
<beneroth>
Regenaxer, though +Fold +Key does not work nicely with (request), as without prefolding the (db) always fails, and with pre-folding.. well :D
<beneroth>
so explicit (unless (db) (new..)) seems necessary