So far, my lexer is pure exercise.
But my goal is actually to filter variables and functions, to see if they are ever used in the code.

> So you got rid of array creation. About time ;)

Yes, that was the only way to get closer to your measured time. :D

On Friday, 15 March 2013 at 08:20:18 UTC, Namespace wrote:
> So far, my lexer is pure exercise.
> But my goal is actually to filter variables and functions, to see if they are ever used in the code.

I'm almost finished. In my few tests, my little parser detects function, struct and variable declarations and expressions. It can resolve rvalue references (by creating temporary variables) and detects unused/underused variables. But it is still a beta. But it makes a lot of fun. :D

On Thursday, 21 March 2013 at 11:36:45 UTC, Namespace wrote:
> On Friday, 15 March 2013 at 08:20:18 UTC, Namespace wrote:
>> So far, my lexer is pure exercise.
>> But my goal is actually to filter variables and functions, to see if they are ever used in the code.
>
> I'm almost finished. In my few tests, my little parser detects function, struct and variable declarations and expressions. It can resolve rvalue references (by creating temporary variables) and detects unused/underused variables. But it is still a beta. But it makes a lot of fun. :D

Moved to https://github.com/Dgame/DAT/

On Saturday, 23 March 2013 at 15:39:50 UTC, Namespace wrote:
> On Thursday, 21 March 2013 at 11:36:45 UTC, Namespace wrote:
>> On Friday, 15 March 2013 at 08:20:18 UTC, Namespace wrote:
>>> So far, my lexer is pure exercise.
>>> But my goal is actually to filter variables and functions, to see if they are ever used in the code.
>>
>> I'm almost finished. In my few tests, my little parser detects function, struct and variable declarations and expressions. It can resolve rvalue references (by creating temporary variables) and detects unused/underused variables. But it is still a beta. But it makes a lot of fun. :D
>
> Moved to https://github.com/Dgame/DAT/

It's time for a beta. Would be nice if someone takes a look at DAT or try it.
I'm sure that there are still some bugs, but maybe this little recreational fun is indeed useful for one or the other.
I had a lot of fun.
It's tested with 'simple.d', std.stdio and std.datetime.

24-Mar-2013 20:08, Namespace пишет:
> On Saturday, 23 March 2013 at 15:39:50 UTC, Namespace wrote:
>> On Thursday, 21 March 2013 at 11:36:45 UTC, Namespace wrote:
>>> On Friday, 15 March 2013 at 08:20:18 UTC, Namespace wrote:
>>>> So far, my lexer is pure exercise.
>>>> But my goal is actually to filter variables and functions, to see if
>>>> they are ever used in the code.
>>>
>>> I'm almost finished. In my few tests, my little parser detects
>>> function, struct and variable declarations and expressions. It can
>>> resolve rvalue references (by creating temporary variables) and
>>> detects unused/underused variables. But it is still a beta. But it
>>> makes a lot of fun. :D
>>
>> Moved to https://github.com/Dgame/DAT/
>
> It's time for a beta. Would be nice if someone takes a look at DAT or
> try it.
> I'm sure that there are still some bugs, but maybe this little
> recreational fun is indeed useful for one or the other.
> I had a lot of fun.
> It's tested with 'simple.d', std.stdio and std.datetime.

Have no time - looks interesting but I highly doubt it can do what is promised. Still take time to do a small formal announcement for beta.

Reusing the old and fizzled out thread of a D lexer to discuss a tool created on top of it is bound to have very little feedback.

-- 
Dmitry Olshansky

> Have no time - looks interesting but I highly doubt it can do what is promised. Still take time to do a small formal announcement for beta.

Yes you're right, it's going to take some time before all would work in general.
In my small test runs, it has, however, been proven, but D is also incredibly complex.
I will also stop very soon to work on it, but maybe the code / the idea inspire someone else to write something more mature for the D community.
This is also the reason why I'm asking in this fizzle thread for a feedback. :)
But once you've taken a look on it, I would be happy if you could tell me what should be improved next time.

On Sunday, 24 March 2013 at 16:54:22 UTC, Namespace wrote:
>> Have no time - looks interesting but I highly doubt it can do what is promised. Still take time to do a small formal announcement for beta.
>
> Yes you're right, it's going to take some time before all would work in general.
> In my small test runs, it has, however, been proven, but D is also incredibly complex.
> I will also stop very soon to work on it, but maybe the code / the idea inspire someone else to write something more mature for the D community.
> This is also the reason why I'm asking in this fizzle thread for a feedback. :)
> But once you've taken a look on it, I would be happy if you could tell me what should be improved next time.

I have similar goals for the Dscananer tool, so I may steal some of your ideas.

On Sunday, 24 March 2013 at 22:16:45 UTC, Brian Schott wrote:
> On Sunday, 24 March 2013 at 16:54:22 UTC, Namespace wrote:
>>> Have no time - looks interesting but I highly doubt it can do what is promised. Still take time to do a small formal announcement for beta.
>>
>> Yes you're right, it's going to take some time before all would work in general.
>> In my small test runs, it has, however, been proven, but D is also incredibly complex.
>> I will also stop very soon to work on it, but maybe the code / the idea inspire someone else to write something more mature for the D community.
>> This is also the reason why I'm asking in this fizzle thread for a feedback. :)
>> But once you've taken a look on it, I would be happy if you could tell me what should be improved next time.
>
> I have similar goals for the Dscananer tool, so I may steal some of your ideas.

I'm glad to hear that. If I can help let me know, would be happy to gain more knowledge in this area.
And I would be glad if some of my ideas become reality.