Re: [X10-users] Char literals and Unicode

It's both. We have not implemented Unicode support in C++, and the parser does not yet understand Unicode in literals and identifiers. There are plans to reimplement x10.lang.String in X10, which would let us pick an encoding for Strings and the representation of Chars that is independent of that

Re: [X10-users] Char literals and Unicode

For compatibility with Java, wouldn't we support Unicode rather than ASCII. I think maybe we don't support Unicode because of the C++ translation (representing Char as a C++ char). Or perhaps it's just that the parser was never implemented to support Unicode. Nate On Tue, Aug 24, 2010 at 19:18

Re: [X10-users] Char literals and Unicode

Indeed, currently Char is so restricted. The primary reason is compatibility with Java, so that x10.lang.String can essentially be implemented as java.lang.String. It does make sense to have a "RichString/RichChar" class as well which supports permits UTF-8. Is there some particular interest i

Re: [X10-users] Help on parser modification

Jeeva Paudel wrote on 08/24/2010 04:03:24 PM: > Hi Nate, > > Thanks for the quick reply. I have lpg already installed in > Eclipse. Assuming you mean, ant build.xml (inside the x10.compiler) > package, I get BUILD SUCCESSFUL message, but the parser still remains > unchanged. Am I missing

Re: [X10-users] Help on parser modification

I don't think you're missing anything, but I haven't rebuilt the grammar in quite a long time. Nate On Tue, Aug 24, 2010 at 15:03, Jeeva Paudel wrote: > Hi Nate, > >     Thanks for the quick reply. I have lpg already installed in Eclipse. > Assuming you mean, ant build.xml (inside the x10.comp

Re: [X10-users] Help on parser modification

Hi Nate, Thanks for the quick reply. I have lpg already installed in Eclipse. Assuming you mean, ant build.xml (inside the x10.compiler) package, I get BUILD SUCCESSFUL message, but the parser still remains unchanged. Am I missing something else here? Jeeva -

Re: [X10-users] Help on parser modification

Jeeva, ant grammar should rebuild the parser, assuming lpg is present. Nate On Tue, Aug 24, 2010 at 13:17, Jeeva Paudel wrote: > Hi all, > >    I tried to regenerate the parser after making some changes in the grammar > (x10.g), but the build does not produce any changes in the parser. I see

[X10-users] Help on parser modification

Hi all, I tried to regenerate the parser after making some changes in the grammar (x10.g), but the build does not produce any changes in the parser. I see that the build file has targets to manage the parser generation, but the relevant files (X10KWLexer, X10KWLexerprs, ..., X10Parsersym) r

[X10-users] Char literals and Unicode

I am reading the X10 Specification and it seems Char literals are restricted to ASCII. Is that correct and if so why? -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative comm

Re: [X10-users] dynamically checked to static?

Try $ x10c -VERBOSE_CALLS Try $x10c -help to see all the flags. Andreas Zwinkau wrote: > Hi, > the compilers shows me how many dynamic checks it inserted: > > $ x10c DataFlowExample.x10 > x10c: 7 dynamically checked calls or field accesses. > > Is there a way to tell, where exactly those dyn

Re: [X10-users] dynamically checked to static?

Hi Andreas, compile with -VERBOSE_CALLS=true This will print details of all inserted dynamic casts. BTW running $ x10c -- -help will print details of the various compiler options. Cheers, Josh On 24/08/10 19:29, Andreas Zwinkau wrote: > Hi, > the compilers shows me how many dynamic checks

[X10-users] dynamically checked to static?

Hi, the compilers shows me how many dynamic checks it inserted: $ x10c DataFlowExample.x10 x10c: 7 dynamically checked calls or field accesses. Is there a way to tell, where exactly those dynamic checks are? Maybe they could be made static with some code changes. Greetings! -- Andreas Zwinkau