When I write a macro, I am usually using a loosely typed object so the
type is not fully known. Even worse, based on the execution path, the
object type may be completely different than expected. Unless your
variables are explicitly stated as to type, it would likely not be possible
to implement.
On 20/08/11 11:41, Henrik Jensen wrote:
Hi Stephan
On 19-08-2011 09:40, Stephan Bergmann wrote:
If I understand the problem correctly: So the hypothetical
code-completion engine has to, at runtime, initialize all kinds of
temp-objects and objects they use and so forth and destroy them
afterwa
Hi Stephan
On 19-08-2011 09:40, Stephan Bergmann wrote:
> On Aug 19, 2011, at 2:06 AM, Henrik Jensen wrote:
>> On 16-08-2011 17:50, Michael Meeks wrote:
>>> On Mon, 2011-08-15 at 23:40 +0100, Henrik Jensen wrote:
Later when I feel more comfortable with the code, I hope to be able to use
On Aug 19, 2011, at 2:06 AM, Henrik Jensen wrote:
> On 16-08-2011 17:50, Michael Meeks wrote:
>> On Mon, 2011-08-15 at 23:40 +0100, Henrik Jensen wrote:
>>> Later when I feel more comfortable with the code, I hope to be able to use
>>> (resurrect ?)
>>> the old GSOC 2006 project
>>> http://wiki.s
