[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Gorm class parser.
From: |
Gregory John Casamento |
Subject: |
Re: Gorm class parser. |
Date: |
Mon, 14 Jul 2008 11:38:21 -0700 (PDT) |
The parser I wrote for Gorm is a recursive descent parser and a pretty simple
one. I didn't want to make yacc and a full up grammer part of Gorm unless I
absolutely had to. Unfortunately it doesn't take the case you spoke of into
account, so it could be a simple matter of adding this to the parser so that it
can be handled properly.
Please do me a favor and **WRITE THIS UP AS A BUG** on savannah instead of
talking about it here so that it can be properly tracked. Also, please send
some example header files which you are having this problem with because I
would like to verify that I see the same behavior with the same files rather
than taking a guess and copying from your email.
Regard, GC
Gregory Casamento -- Principal Consultant - OLC, Inc
# GNUstep Chief Maintainer
----- Original Message ----
From: Marko Riedel <markoriedelde@yahoo.de>
To: DISCUSS GNUstep <discuss-gnustep@gnu.org>
Sent: Monday, July 14, 2008 11:33:12 AM
Subject: Gorm class parser.
Hi folks,
I have come across a problem in the classloader of Gorm.app. I ask your
understanding when I say it is not terribly sophisticated. I had noticed that
declarations of several instance variables of the same type like so
NSMutableArray *a1, *a2,
would confuse it, resulting in corrupted outlet lists, so now I always write
NSMutableArray *a1;
NSMutableArray *a2;
Now I have another, more serious problem: it appears that the parser will
consider everything an outlet that contains the string "id", e.g.
NSMutableDictionary *namesToPids;
will cause "namesToPids" to appear in the outlet list. This is an annoying
problem and I don't think not to use the string "id" in variable names is an
acceptable solution (though using "namesToPIDs" will fix it).
Anyhow I hope you can replicate this, if not, please accept my apologies.
BTW does GNUstep have a regexp libary yet that offers, say Perl-compatible
regular expressions with different enodings (utf8 ...)?
Best regards,
Marko
+-------------------------------------------------------------+
| Marko Riedel, EDV Neue Arbeit gGmbH, markoriedelde@yahoo.de |
| http://www.geocities.com/markoriedelde/index.html |
+-------------------------------------------------------------+
__________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com
_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
- Gorm class parser., Marko Riedel, 2008/07/14
- Re: Gorm class parser.,
Gregory John Casamento <=