| Time |
Nick |
Message |
| 00:05 |
|
FileX joined #luanti |
| 01:16 |
|
SFENCE joined #luanti |
| 01:41 |
|
sys4 joined #luanti |
| 01:49 |
|
SFENCE joined #luanti |
| 03:25 |
|
SFENCE joined #luanti |
| 03:51 |
|
FileX joined #luanti |
| 04:00 |
|
MTDiscord joined #luanti |
| 05:16 |
|
FileX joined #luanti |
| 05:24 |
|
Warr1024 joined #luanti |
| 05:48 |
|
Verticen joined #luanti |
| 06:00 |
|
bodiccea joined #luanti |
| 06:23 |
|
SFENCE joined #luanti |
| 06:47 |
|
Kimapr joined #luanti |
| 06:49 |
|
FileX joined #luanti |
| 06:53 |
|
Meli joined #luanti |
| 07:04 |
|
SFENCE joined #luanti |
| 07:16 |
|
SFENCE joined #luanti |
| 08:05 |
|
FileX joined #luanti |
| 08:32 |
|
lemonzest joined #luanti |
| 08:34 |
|
SFENCE joined #luanti |
| 08:43 |
|
SFENCE joined #luanti |
| 08:52 |
|
SFENCE joined #luanti |
| 09:03 |
|
SFENCE joined #luanti |
| 09:14 |
|
SFENCE joined #luanti |
| 09:22 |
|
SliverFlowCipher joined #luanti |
| 09:24 |
|
SFENCE joined #luanti |
| 09:32 |
|
SFENCE joined #luanti |
| 09:59 |
|
SFENCE joined #luanti |
| 10:11 |
|
FileX joined #luanti |
| 10:25 |
|
SFENCE joined #luanti |
| 10:59 |
|
SFENCE joined #luanti |
| 11:12 |
|
SFENCE joined #luanti |
| 11:38 |
|
SFENCE joined #luanti |
| 11:42 |
|
SFENCE joined #luanti |
| 12:19 |
|
SliverFlowCipher joined #luanti |
| 12:34 |
|
ireallyhateirc joined #luanti |
| 15:05 |
|
diemartin joined #luanti |
| 15:47 |
|
SFENCE joined #luanti |
| 16:05 |
|
kamdard joined #luanti |
| 16:23 |
|
Mc joined #luanti |
| 16:45 |
|
fluxionary joined #luanti |
| 17:04 |
|
jaca122 joined #luanti |
| 18:37 |
|
Talkless joined #luanti |
| 18:48 |
|
jemius joined #luanti |
| 19:00 |
|
SFENCE_ joined #luanti |
| 19:23 |
|
SFENCE joined #luanti |
| 19:39 |
|
kamdard joined #luanti |
| 19:53 |
|
SFENCE joined #luanti |
| 20:20 |
|
silverwolf73828 joined #luanti |
| 20:21 |
|
Verticen joined #luanti |
| 20:28 |
luk3yx |
Mod storage appears to write multiple keys atomically if I set two keys without giving control back to C++ (i.e. storage:set_string("key1", "value1"); storage:set_string("key2", "value2")). Can I rely on this behaviour or is it an implementation detail that might change in the future? |
| 20:43 |
Krock |
luk3yx: huh? l_set_string is a C++ function that's called |
| 20:44 |
Krock |
or does the "storage" object refer to a Lua-only implementation of some sort? |
| 20:45 |
luk3yx |
Sorry, that wasn't a great way of explaining it, the C++ code that saves mod storage is saved in Server::AsyncRunStep, so if I call storage:set_string twice without returning from my function the saving code won't ever get run. |
| 20:45 |
luk3yx |
s/ever get run/get run until after both values are changed/ |
| 20:46 |
|
SFENCE joined #luanti |
| 20:47 |
Krock |
that's correct. I'll be in memory but not written to disk until later |
| 20:48 |
Krock |
the time when it will be written is afaik not specified, but it eventually will be written, just like the changed mapblocks. |
| 20:54 |
|
TheCoffeMaker joined #luanti |
| 20:55 |
luk3yx |
Okay, thanks |
| 21:06 |
Krock |
You're welcome. |
| 21:08 |
|
SFENCE joined #luanti |
| 21:42 |
|
SFENCE joined #luanti |
| 22:01 |
|
SFENCE joined #luanti |
| 22:17 |
|
Kimapr joined #luanti |
| 22:32 |
|
swee joined #luanti |
| 22:41 |
|
SFENCE joined #luanti |
| 23:32 |
|
panwolfram joined #luanti |
