Re: Exceptions & OPIE?

Erik Hovland <[email protected]>
Newsgroups gmane.comp.handhelds.opie.devel
Message-ID <[email protected]>
On Sat, Jun 10, 2006 at 08:21:32PM +0200, Patrick Hoffmann wrote:
> On Sat, 10 Jun 2006 19:47:32 +0200, Erik Hovland <[email protected]> wrote:
> >I don't know specifically why Opie uses that flag. But I do know that
> >generally gcc native exceptions can expand the size of binaries on
> >embedded systems like arm and powerpc.
> 
> Hm - I have to compile for arm. So I should mind that ;(
> 
> >Is there any way that you could substitute macros for your exception
> >handling that would allow for exceptions when present and melt away when
> >not?
> 
> I can replace the exceptions (only a few). But I'm interested, because I'm  
> workin on a library  that uses exceptions and it would be great if this  
> wont be a problem on embedded systems. Do you know where I can get more  
> information about this issue? May be... a document?

This is the best I could turn up with a few minutes of googling:
http://www.oesf.org/forums/lofiversion/index.php?t16202.html
http://www.pnp-software.com/ObsFramework/doc/indexImplementationIssues.html

This idea is pretty vague. But, Qt/E does provide a complete
event/callback system. If you can stand it, you could probably rig a
simple event system which emulates exceptions.

There are libraries for embedded systems that have implemented their own
exception system to deal with the issue of bloat in gcc native
exceptions. ACE/TAO is one of those systems:
http://www.cs.wustl.edu/~schmidt/TAO.html

You could look at their code for background.

E

-- 
Erik Hovland
mail: [email protected]
web: http://hovland.org/
PGP/GPG public key available on request
_______________________________________________

http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex

Opie-devel mailing list
[email protected]
https://handhelds.org/mailman/listinfo/opie-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.