2.4.0 Release preparation

Long term todo's for 2.4.0 release

Remove legacy interfaces and compatibility

removing old socket routines

edit

since nobody did anything about this at all since 2.2.0 was released, is it really a good idea to start completely throwing that stuff around now right before the next release? -- Jonas

The agreement then was afaik to kill it off just before 2.4.0, to avoid having long ifdef's in user code between 2.2 and 2.3.1 (the oldlinux problem we had with 1.0 and 1.9.x).

But you are right that it might be too late for the passock part. So I suggest to keep that part for another round, since they are flagged deprecated anyway, and only remove the aliases that have 1:1 fp* equivalents since 1.9.x days. Moreover, the upcoming release is a beta. Its interface should be correct, but minor bugs can be fixed in the real release, if their potential problem scope is as little as this one. -- Marco