Hi,
* Tony Balinski wrote (2008-01-06 03:06):
>Quoting Thorsten Haude <[EMAIL PROTECTED]>:
>> * Thorsten Haude wrote (2008-01-06 01:40):
>> >char *AllocString(int length)
>> >{
>> > [...]
>> >}
>> >
>> >- Also, it returns (mem + sizeof(char *) + 1), which is (char* +
>> > size_t + int). What is this supposed to bring about?
>>
>> A bunch of function test whether AllocString's return value is True or
>> False. This happens if XtMalloc() returns -(sizeof(char *) + 1).
>
>Good point! But then, as you pointed out not long ago, XtMalloc failure in
>nedit results in exit().
Well yeah, but the question is whether we should keep it that way.
Also, I do not seem to be the only person confused about NEdit
sometimes. (Which makes me feel kinda... understood.) Someone put in
these checks.
Thorsten Esther Phillips: Release Me
--
Trying to make bits uncopyable is like trying to make water not wet.
The sooner people accept this, and build business models that take
this into account, the sooner people will start making money again.
- Bruce Schneier
pgpI0CmeA2o0k.pgp
Description: PGP signature
-- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
