Re: NewEra: NE_DATA segment

> Can anybody tell me, what information is stored in the data segment > called NE_DATA ? This segment has reached the limit of 64kb in my > application and now i cant't run p-code anymore. I found out that using > complex types in class definition as "PUBLIC VARIABLE str ixString" > causes the segment to be blown up by hundreds of bytes. With this > information I managed to compile c-code again, but p-code still gives > me a "MEM_ALLOC_ZERO" from smartheap library at startup. The NE_DATA problem can be solved by breaking up the application into DLLs and moving global/shared variables into these DLLs. I'm not too sure whether the cause is the use of complex types. I suspect it is the use of global/shared variables. The p-code problem could be the same as above but it is more likely to be the 64k limit on function name space in your 4gi. In which case, use DLLs or shorten your function/handler names so that the total length fits inside 64k. > --- _ > // Tom Beuke Mail : > tob@blanker.ruhr.de > _ // Westhoffstr.13-15 Tel. : +49 231 839757 > \\X/ 44145 Dortmund > --- > 5 Kilometer zum Nachbarn, 18 Kilometer zum Arzt, 889 Kilometer zur > Tochter, > 3 Schritte zum Telefon, 2000,-DM Telefonrechnung im Monat ... David W Chan GO5 Limited dwc@cix.compulink.co.uk