I am not so sure that will help us.
What are the pros what the cons?
Am 17. April 2018 08:13:33 MESZ schrieb Damjan Jovanovic :
>The Mozilla project also uses C++, also started in a similar timeframe
>to
>StarOffice, also has a huge codebase, also uses a component-based
>development methodology, a
The Mozilla project also uses C++, also started in a similar timeframe to
StarOffice, also has a huge codebase, also uses a component-based
development methodology, and so on.
Lately, they've dealt with memory issues by developing in another language
that is memory-safe: Rust.
We could learn from
I would like to pick the discussion up again.
In general I prefer a Class type approach over a Function based approach
in Code methology. Since Class based has the "buildIn" RAI approach, I
think the pool approach does not make sense when classes are used. When
ever the desicion goes in favour
A related problem to consider is the generally poor runtime environment
support for using C++ between modules. On Windows, using C++ between
different DLLs requires they were built by the same MSVC version and used
the same CRT runtime settings, and I am finding that for the main/jvmaccess
module t
On 3/25/2018 10:44 AM, Pedro Giffuni wrote:
> Somewhat related ...
>
> I have been considering the use of APR pools:
>
> http://www.apachetutor.org/dev/pools
>
> It would be great to have the memory managed by the same technology used
> in Apache httpd.
I need to think about this. It seems v
On 25.03.2018 21:28, Patricia Shanahan wrote:
On 3/25/2018 10:44 AM, Pedro Giffuni wrote:
Somewhat related ...
I have been considering the use of APR pools:
http://www.apachetutor.org/dev/pools
It would be great to have the memory managed by the same technology
used in Apache httpd.
I need
On 3/25/2018 10:44 AM, Pedro Giffuni wrote:
Somewhat related ...
I have been considering the use of APR pools:
http://www.apachetutor.org/dev/pools
It would be great to have the memory managed by the same technology used
in Apache httpd.
I need to think about this. It seems very appropriate
Somewhat related ...
I have been considering the use of APR pools:
http://www.apachetutor.org/dev/pools
It would be great to have the memory managed by the same technology used
in Apache httpd.
Cheers,
Pedro.
-
To unsubs
Documents that are to large for the memory available will also fail to
load in the 1st approach.
To add array review mechanism is in my opinion only a source of errors.
I think STL should be used.
+1 for not hiding the exceptions. Maybe we could catch exception on
document level quickly and pr
