Hi:
My point was that I think Joe Armstrong's view
might be robust, but I'm not sure it's always practical.
You can't directly compare that to the exception::what()
or event queue,
because he's talking about an environment where
each message (a new CA monitor, an error message, ...)
is passed between processes which can't share anything.
So the database posting a monitor and channel access queuing it,
or the exception thrower and the catcher,
would all be different processes,
pointers wouldn't work between them.
He also envisions some global garbage collector.
I think java is somewhere in between:
You can still share pointers between threads,
but only pointers to objects, not types like 'double'.
and you have garbage collection.
That's already easier to use than C/C++,
and you don't enter yet another string-related discussion
with every API that anybody suggests for anything.
But at the same time, java is already slower than C/C++,
and I wonder about the performance of Erlang.
-Kay
- Replies:
- Re: Erlang Benjamin Franksen
- References:
- RE: XML is dead, long live ML9 Jeff Hill
- Navigate by Date:
- Prev:
Re: (A)synchronous dbGetLink Benjamin Franksen
- Next:
More on the evils of referencing: Iterators verses Callbacks Jeff Hill
- Index:
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: XML is dead, long live ML9 Jeff Hill
- Next:
Re: Erlang Benjamin Franksen
- Index:
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|