I think that what we should get is
Compiler compile: 'text' with: aCompilingContext
aCompilingContext should hold the information about
where: in
classified:
failing
noytfying
....
Stef
On Nov 3, 2009, at 10:32 PM, Igor Stasenko wrote:
> 2009/11/3 Lukas Renggli <[email protected]>:
>>> Well, I can rename the compile: method and post to PharoInbox, if
>>> anyone is interested.
>>
>> Also I agree that it is confusing, but there are tons of projects
>> that
>> depend on this function. #compile: and #compile:classified: are about
>> the only two compiler related methods that are available cross
>> platform. If you rename them you will break any code that compiles
>> something, including the Refactoring Browser, SmaCC, OmniBrowser,
>> Seaside (for the file libraries), etc.
>>
> You are right , of course.
>
> But inner API should be simplified.
> For instance, take a look at compiler invocation here:
>
> self compilerClass new
> compile: code
> in: self
> classified: category
> notifying: requestor
> ifFail: failBlock.
>
> i really don't understand, why compiler would be interested in a
> method's category?
> What is the purpose of passing this extra info to compiler?
> The main purpose of compiler is to produce the CompiledMethod
> instance, and compiler should not care
> about anything related to installation of the resulting method into
> class and its categorization.
>
>
>> Lukas
>>
>> --
>> Lukas Renggli
>> http://www.lukas-renggli.ch
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
