From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: NTFS file system driver (update 4)
Date: Sat, 10 Nov 2007 18:35:00 +0100 [thread overview]
Message-ID: <87bqa2dmwr.fsf@xs4all.nl> (raw)
In-Reply-To: <ca0f59980708030136hafbb0b8r27922dc932b8ad23@mail.gmail.com> (bean123ch@gmail.com's message of "Fri, 3 Aug 2007 16:36:39 +0800")
Bean <bean123ch@gmail.com> writes:
> On 8/3/07, Marco Gerards <mgerards@xs4all.nl> wrote:
>> Bean <bean123ch@gmail.com> writes:
>>
>> > On 8/3/07, Marco Gerards <mgerards@xs4all.nl> wrote:
>> >> Bean <bean123ch@gmail.com> writes:
>> >>
>> >> >> If you make these two changes and send in the patch, I'll commit the
>> >> >> patch.
>> >> >>
>> >> >
>> >> > Ok, this is the new patch.
>> >>
>> >> Committed.
>> >>
>> >
>> > Thanks, but i don't see fs/ntfs.c in the cvs, do you forget to add it ?
>>
>> Yes, I forgot it, but now it is really committed.
>>
>> > As ntfs driver is done, i start to work on the scripting support. Does
>> > the parser in the previous test program ok ?
>>
>> To be honest, I just didn't find the time yet :(.
>>
>> Actually, I hoped you could first update the other patch regarding
>> scripting. There was one part of the patch I didn't like. If you can
>> take that out, at least the other parts can be committed without much
>> of a problem.
>
> Which part ? Do you mean the new lexer code in grub_script_yylex2 ?
Yes.
>> About that other parser file? Personally I don't like it if you would
>> start from working from scratch on the parser. The way ASTs and stuff
>> are build now is just fine, although not perfect. However, if you
>> improve the current parsing rules that would be great. I do not have
>> much time today, so if I will not have the time today, I'll try to
>> look after this weekend.
>>
>
> Yes, we can just use the parsing rules, AST and related stuff will
> remain the same.
>
> But I think the lexer code need to be changed, the current lexer will
> break the following token:
>
> "aa$BB"
>
> into aa and $BB, but in fact, it should act as one.
I will look into this problem soon. At the time I just ignored it to
speed up the implementation, sorry for that.
Do you object if the other part is applied? I would appreciate it if
you had the time to make a new patch...
--
Marco
prev parent reply other threads:[~2007-11-10 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 20:10 NTFS file system driver (update 4) Bean
2007-08-02 17:01 ` Marco Gerards
2007-08-02 18:10 ` Bean
2007-08-02 18:36 ` Marco Gerards
2007-08-02 18:52 ` Bean
2007-08-02 20:24 ` Marco Gerards
2007-08-03 2:06 ` Bean
2007-08-03 8:01 ` Marco Gerards
2007-08-03 8:36 ` Bean
2007-11-10 17:35 ` Marco Gerards [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bqa2dmwr.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.