I have probably asked this before, but things might have changed. What is the situation for a parser application that uses gelex and geyacc built parser, for...
... gelex does not support unicode. It only supports 8-bit character input stream. However you can consider your unicode files as a sequence of bytes...
Dear all, I built some ISO8601 date/time classes, and some initial test cases. If anyone wants to use this material for Gobo, you are welcome. The classes are...
... Tokens are element names, attribute names, strings, ... If it were to parse Eiffel classes containing unicode characters, the tokens would be identifiers,...
In our gelex/geyacc archetype parser I have a state during which text in a sub-syntax is consumed. The lexer is in that state when the EOF is reached. The...
... I don't think so. If instead of <<EOF>> it was a "real" token, you could do: less (text_count) But it will not work with <<EOF>>. ... I tried the...
... I don't know what you mean by "normal" gelex/yacc classes. Even if unicode characters are inside "", they are still a sequence of bytes for the scanner. So...
GEC generates bad C code for some of my external routines in secom. However the external compiles correctly on SmartEiffel 1.0 and ES 5.6. Here is the Eiffel...
... As far as I know GEC implements what is specified in ECMA Eiffel. You would have to write: c_set_read_total_constant (an_item: POINTER; a_value: INTEGER)...
... Presumably the extra semicolon will still work with ISE and SE because I guess they will probably just generate C code with ";;" which is still valid C....
... I remember now. I figured out how to make statements work with all three compilers by adding a semi-colon, just as you suggested. What I couldn't figure...
... I think ECMA says it should be: sizeof: INTEGER is -- Size to allocate (in bytes) external "C inline use <windows.h>" alias "return sizeof (struct...
... Could gec generate "return ALIAS-CONTENT;" if there's no 'return' in the alias content. Then it can be both ECMA- and legacy 'compliant'. (With a warning...
... The disadvantage to the ECMA approach with inline functions is that things like stack tracing and assertions are more difficult to implement. Take a look...
... At worst you have to add a wrapper function that contains the assertions/stack tracing, and calls a C function with the raw alias content. Not difficult!...
... The idea behind ECMA's specification is to allow the inclusion of the code of C functions into Eiffel classes without having to write a C file. That's why...
... Okay, I think the ECMA way is best because it's so simple to understand. Eric, will you attempt to support both ECMA and legacy style? Thanks again, Brian...
... It's now in CVS. Note that what is implemented is stupid: it just looks for the string "return" in the alias, without any assumption about the C syntax. So...
... Okay, it works. Note that I still had to add a semi-colon to the end of every statement. I tested with SE and ISE, with and without assertions, and in...
Hello. I would like to play around with XML and XPATH, but as I added the following local variable: xpe: XM_XPATH_EXPRESSION and compiled with F7, then I got...
Thank you both for replying my request. I just use the latest version of Eiffel Studio, and thus the embedded GOBO library. Actually, I found out to insert a...
