barrels and memory

is barrel code/data consumes main app memory or it run like external DLL/API so I can move some utils function to barrel and save main app memory?

0 jim_m_58 over 2 years ago

A barrel is compiled in to your prg and is in your same memory space and in fact adds a bit of additional overhead.

0 _psx_ over 2 years ago in reply to jim_m_58

So, no any advantage, is it mean barrel is binary?

0 peterdedecker over 2 years ago in reply to _psx_

it's basically the same implementation as a module which just happens to be zipped (and only supports ciq 2.4+ projects)

0 _psx_ over 2 years ago in reply to peterdedecker

So, I can unzip barrel put source (that I can even fix of needed} into source directory,, compile, save memory {or not save if module also takes additional memory}.

So question is, why is barrel for? :-)

0 jim_m_58 over 2 years ago in reply to _psx_

It's to share code with other users. If you look at a .barrel file, it's basically just a zip of the barrel project that gets unzipped and compiled when you compile the app..

With my barrels, I often use jungles to just use the source code without actually using the barrel, to save the overhead of using the .barrel file.