[ragel-users] BUG while processing import directive

[Denis Naumov]

Sorry - sorry - sorry
my english so poor :))))

this text without typos.

=========================================

Thanks, Josef.

I know about patching with '\' processing.

but, it seems to me that the best way is to convince Adrian to make
these changes to the original source code.

You have you own ragel build.
I have my own ragel build.
Somebody have his own build.

At this time you forgot to do patch.
Next time i forgot to do this.
Or someone does not know that this was a such problem and not do
the patch at all.

If Adrian makes a change to the original source code - problem will
cease to exist in all future versions.

It is important to find just the easiest way that would require a
minimum of changes in the source code and will not affect the build
for other operating systems.

Best regards.
Denis.





2011/7/11 Denis Naumov <alexander.me at gmail.com>:
> Thanks, Josef.
>
> I know about patching whit '\' processing.
>
> but, it seems to me that the best way is to convince Adrian to make
> these changes to the original source code.
>
> You have you own ragel build.
> I have my own ragel build.
> Somebody have his own build.
>
> At this time you forgot to do patch.
> Next time i fogot to do this.
> Or someone does not know that this was a problem in general and not do
> the patch at all.
>
> If Adrian makes a change to the original source code - problem will
> cease to exist in all future versions.
>
> It is important to find just the easiest way that would require a
> minimum of changes in the source code and will not affect the build
> for other operating systems.
>
> Best regards.
> Denis.
>
>
> 2011/7/11  <ragel-user at jgoettgens.de>:
>> Denis,
>>
>> The VS version has been updated to properly take of '\' in file names, even
>> for the import statement. Unfortunately this does not solve you problem. I
>> found that bogus imports cause an exception inside the function do_scan()
>> triggered by line "int len = input.gcount()".
>>
>> I have also added the early return statement as you suggested. At least with
>> the simple test project inside Ragel\tests Ragel no longer crashes.
>>
>> jg
>>
>>
>> _______________________________________________
>> ragel-users mailing list
>> ragel-users at complang.org
>> http://www.complang.org/mailman/listinfo/ragel-users
>>
>

_______________________________________________
ragel-users mailing list
ragel-users at complang.org
http://www.complang.org/mailman/listinfo/ragel-users