This Forum is Dedicated For all The Object Oriented PIC Lovers .......... The concept behind OOPic is straight forward. Use preprogrammed multitasking Objects from a library of highly optimized Objects to do all the work of interacting with the hardware. Then write small scripts in Basic, C, or Java syntax styles to control the Objects. During operation, the Objects run continuously and simultaneously in the background while the scripts run in the foreground telling the objects what to do.

Sunday, March 9, 2008

Re: [oopic] Error 23 -- Objects have exceded available RAM

This means that you will need to reduce your object usage. Either
re-use some objects by re-linking at different parts of the program (the
ooPIC has no garbage cleanup) or use lower-resource objects. As Richard
says, you can also try using BYTE or WORD variables instead of oBYTE or
oWORD if they aren't linked to a VC.

DLC

jporterwbtcorp wrote:
> Hello..
>
> I am compiling a rather large program on an OOpicII B.2.2+ and I'm
> getting the following message -- Error #23, objects have exceeded the
> available RAM by XXX bytes
>
> Is this a hardware limitation in the oOpic chip itself or can I remedy
> this by installing a bigger eprom? If another eprom is the answer,
> could you please specify what to use? Thanks.
>
> John
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>

--
------------------------------------------------------
Dennis Clark ooPIC Tech Support
www.oopic.com
------------------------------------------------------


Yahoo! Groups Links

<*> To visit your group on the web, go to:

http://groups.yahoo.com/group/oopic/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:

http://groups.yahoo.com/group/oopic/join

(Yahoo! ID required)

<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:

http://docs.yahoo.com/info/terms/

No comments: