I do not think it works for gemstone because apparently they cannot access the
parser
or at least wants to make sure that you cannot write code that can break the
server
scenario: you are mean that you write a strange meta data that is
executed on the server
so I will take tirade parser and make sure that we get one that only
parse literal arrays.
On Apr 24, 2012, at 3:23 PM, Igor Stasenko wrote:
> Here the the snippet to parse array literals.. based on existing parser..
> i only had to add a #parseNode accessor to Parser to make it work:
>
>
> | parser|
> parser :=
> (Parser new
> init: '#(1 2 3 (ab bc de))' readStream notifying: nil failBlock: []
> ).
>
> parser encoder initScopeAndLiteralTables.
> parser primaryExpression.
> parser parseNode key
>
>
>
> On 24 April 2012 15:19, Stéphane Ducasse <[email protected]> wrote:
>> goran could I extract the parser? and rename it in another package?
>>
>> Stef
>>
>> On Apr 24, 2012, at 12:00 PM, Göran Krampe wrote:
>>
>>> On 04/24/2012 11:52 AM, Göran Krampe wrote:
>>>> On 04/24/2012 11:51 AM, Göran Krampe wrote:
>>>>> On 04/24/2012 11:46 AM, Stéphane Ducasse wrote:
>>>>>> Where is the code?
>>>>>
>>>>> On SS. But it seems... down? Project is called "Tirade".
>>>>
>>>> http://www.squeaksource.com/Tirade.html
>>>
>>> Eh, oops. I just realized that TiradeParser uses dynamic arrays { } and
>>> does not have current support for literal Arrays. Duh. Sorry about that,
>>> but feel free to use the code anyways, adding #parseLiteralArray should not
>>> be hard.
>>>
>>> regards, Göran
>>>
>>
>>
>
>
>
> --
> Best regards,
> Igor Stasenko.
>
