I agree that one should not have identifiers differing only in case. However, I think, case-insensitive languages lead to inconsistent code, especially for newbies: I currently take a Astrophysics lecture where we program in FORTRAN. Most of my colleges have never written a program before and they have never learned writing good looking source: DO ii = 1,5 if mod(Il, 2) = 0 Then Write(*,*) Ii END if end do Not really easy to find bugs like this, I think ;) Sorry, my example is bad, it was just a silly idea of mine how I could resolve my problem. The real thing is the following: I am trying to parse Smalltalk code inside a completely different grammar, similar to what you did with the SmallWiki parser. My parser stripped down to the problem is the following, the scanner is similar to StScanner in the SmaCC examples: Method : Selector Condition? Body { ... } ; Selector : (<keyword> Pattern)+ { ... } ; Pattern : <name> { ... } ; Condition : "if:" "[" { parse smalltalk block } ; Body : { parse smalltalk method body } ; When giving input like a: anA b: aB if: [ ... ] ^self I get a: anA b: aB if: [ Token not expected ->... ] ^self even before my code { parse smalltalk block } is evaluated. Similar when giving a: anA b: aB ^self I get a: anA b: aB Token not expected ->^self before I even had a chance to start the RB parser in { parse smalltalk method body }. I expect that I'm doing something completely wrong, but can't find the problem. I also tried to go with the debugger through the SmallWiki parser, but there it just works and I don't see any significant difference. Thanks a lot for your help, Lukas -- Lukas Renggli http://renggli.freezope.org

The following problems reported by John Brant have been fixed: I changed the behavior and I think this enhances the usability a lot. Additionally I've also modified the internal representation of children in the folders: they are now stored in a dictionary (id -> structure) instead as an ordered collection, what enhances lookup-speed a lot. I used an ordered collection in the past because folders were rendered automatically before, but now as they behave like an ordinary page there is no more need to keep the pages in a certain order. As the internal data-structure changed, existing wikis have to be migrated. The post-load action will evaluate the following code: Folder>>migrateOrderedCollectionToDictinary | childrenInstVarIndex old | childrenInstVarIndex := self allSuperclasses inject: (self instVarNames indexOf: 'children') into: [ :sum :each | sum + each instVarNames size ]. self allInstancesDo: [ :folder | old := folder instVarAt: childrenInstVarIndex. (old isKindOf: SequenceableCollection) ifTrue: [ folder instVarAt: childrenInstVarIndex put: folder defaultChildrenCollection. old do: [ :child | folder add: child ] ] ] These two bugs have been fixed, I forgot to encode strings in the attributes of the html-tags properly. Another thing I've fixed are the recent changes: it displays a page at most once a day, even if it has been edited several times. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Wow, thanks a lot for this code-snippet. I included it into my parser and all the tests immediately passed. Shouldn't this be a checkbox in the SmaCC-UI to allow generating this method automatically? Or are there any problems to be expected when adding this code? I tried all kinds of valid and invalid input and it works as expected with my example. Regards, Lukas -- Lukas Renggli http://renggli.freezope.org