in reply to Moving an OP and replacing it

In C, it is sometimes appropriate to fiddle with the allocation of objects. In perl, the natural paradigm is to allow garbage collection to eliminate obsolete data, and new objects to be allocated where they will.

Why do you want to allocate things in particular locations? Maybe you should create an object with Inline::C handling the details, if you REALLY need it ... but I bet you don't need it.

--
TTTATCGGTCGTTATATAGATGTTTGCA

Replies are listed 'Best First'.
Re: Re: Moving an OP and replacing it
by diotalevi (Canon) on Jun 01, 2004 at 02:19 UTC
    I am attempting to do something s///-like on the optree which implies that either the object being replaced must either be altered (the move/replace I mentioned) or the pointers to it must be adjusted.