On 22 Mar 2010, at 16:42, Dimitri Smits wrote:
> WHAT C++ compiler-mangling are you going to support?
The compiler currently only supports G++ 3.x and later.
Jonas
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/
Jonas Maebe wrote:
>
>On 22 Mar 2010, at 11:19, Anton Kavalenka wrote:
>
>> Don't UNITS in Pascal intended to separate NAMESPACES?
>> But unfortunately this prevents nested namespaces.
>
>The discussion is not about adding support for C++-style namespaces to Pascal,
>but for how to specify the C+
Jonas Maebe wrote:
On 22 Mar 2010, at 11:19, Anton Kavalenka wrote:
Don't UNITS in Pascal intended to separate NAMESPACES?
But unfortunately this prevents nested namespaces.
The discussion is not about adding support for C++-style namespaces to Pascal,
but for how to specify the C++
On 22 Mar 2010, at 11:19, Anton Kavalenka wrote:
> Don't UNITS in Pascal intended to separate NAMESPACES?
> But unfortunately this prevents nested namespaces.
The discussion is not about adding support for C++-style namespaces to Pascal,
but for how to specify the C++ namespace in which an (ext
Florian Klaempfl wrote:
5. What's the best way to save the namespace in the tobjectdef class?
As a string containing 'FirstPart.SecondPart'? Or as C++ mangled
string '9FirstPart10SecondPart'? Or something else (e.g. a list
containing the parts)?
I've decided to save the mangled name in th
Hi again!
On 21.03.2010 15:24, Marco van de Voort wrote:
In our previous episode, Sven Barth said:
(besides using m_none instead of m_all as Jonas mentioned).
I'm talking about the namespace value itself.
E.g. the C++ code
namespace Foo::Bar {
class FooBar {
}
}
becomes to
In our previous episode, Sven Barth said:
> (besides using m_none instead of m_all as Jonas mentioned).
>
> I'm talking about the namespace value itself.
>
> E.g. the C++ code
>
> namespace Foo::Bar {
> class FooBar {
>
> }
> }
>
> becomes to
>
> FooBar = cppclass
>
> end; namesp
Hi again!
Once I say 'I did it that and that way', all are coming to answer me...
Nice :)
On 21.03.2010 14:28, Paul Ishenin wrote:
21.03.2010 20:21, Sven Barth wrote:
3. How can I parse a not reserved identifier? Checking "idtoken" for
"_ID", using it with "token" and after usage calling "co
21.03.2010 20:30, Jonas Maebe wrote:
That should be "m_none" instead of m_all, otherwise every program
using "namespace" as identifier will fail to compile afterwards.
Sorry. My fault - looked at m_none but copied m_all line instead :(
Best regards,
Paul Ishenin.
___
>> 5. What's the best way to save the namespace in the tobjectdef class?
>> As a string containing 'FirstPart.SecondPart'? Or as C++ mangled
>> string '9FirstPart10SecondPart'? Or something else (e.g. a list
>> containing the parts)?
>
> I've decided to save the mangled name in the objectdef. It's
On 21 Mar 2010, at 14:28, Paul Ishenin wrote:
> 21.03.2010 20:21, Sven Barth wrote:
>>> 3. How can I parse a not reserved identifier? Checking "idtoken" for "_ID",
>>> using it with "token" and after usage calling "consume(_ID);"?
>>
>>
>> Usage is with "pattern" (all letters uppercase) or "or
21.03.2010 20:21, Sven Barth wrote:
3. How can I parse a not reserved identifier? Checking "idtoken" for
"_ID", using it with "token" and after usage calling "consume(_ID);"?
Usage is with "pattern" (all letters uppercase) or "orgpattern"
(original casing) instead of "token"... the rest works
Hi again!
I'll answer some of my questions myself:
2. What about the order of namespace and external? Should it be "namespace (...); external
(...);" or "external (...); namespace (...);"? Or shall both orders be accepted?
For now I've decided to use "namespace(...); external(...);"
3. Ho
Hi again!
On 21.03.2010 11:28, Paul Ishenin wrote:
> 21.03.2010 17:08, Sven Barth wrote:
>> 4. What about reserved identifiers being used in the namespace which
>> might be valid in C++ (e.g. "location", "platform", "register",
>> "object" or even "begin")?
> '&' at the begining of identifer allo
In our previous episode, Paul Ishenin said:
> > That doesn't help, since still breaks existing code that might not even use
> > C++ extensions. But I assume this is done in a separate mode (or
> > modeswitch?)
> >
> Sorry? & needs to be placed in the pascal code. So I don't see what
> existing
21.03.2010 17:33, Marco van de Voort wrote:
'&' at the begining of identifer allows to use any identifier name like
&location,&platform, etc.
That doesn't help, since still breaks existing code that might not even use
C++ extensions. But I assume this is done in a separate mode (or
modeswi
In our previous episode, Paul Ishenin said:
> 21.03.2010 17:08, Sven Barth wrote:
> > 4. What about reserved identifiers being used in the namespace which
> > might be valid in C++ (e.g. "location", "platform", "register",
> > "object" or even "begin")?
> '&' at the begining of identifer allows t
21.03.2010 17:08, Sven Barth wrote:
4. What about reserved identifiers being used in the namespace which
might be valid in C++ (e.g. "location", "platform", "register",
"object" or even "begin")?
'&' at the begining of identifer allows to use any identifier name like
&location, &platform, etc.
18 matches
Mail list logo
