Scripting languages and IDEs

Hernan Wilkinson hernan.wilkinson at mercapsoftware.com
Thu Aug 24 15:28:43 UTC 2006


Ralph Johnson wrote:

> On 8/24/06, Oscar Nierstrasz <oscar at iam.unibe.ch> wrote:
>
>> Hm.  But my Ruby scripts consist of class definitions and methods,
>> and then a call to single method.
>
>
> Ruby has to do it this way because it doesn't have an image.

>
> To me, scripting isn't very OO.  However, a good scripting system
> needs proper domain abstractions.  OO is good for defining the domain
> abstractions.  If you just want to bash some files, you don't need to
> define new classes.  But if you want to think of the files as "Paper
> Reviews" or "Job Applications" then you will want to make some
> classes.

I think that a scripting system should allow the user to decompose the 
problem into smaller ones, because if not, the script could be ending in 
a 100 lines of plain code... and at the same time I think that classes 
and objects are too much for the type of problems that one specs to 
solve when scripting...
Therefore (and don't kill me for this idea), I think the script language 
should support the definition of "procedures or functions" and no more 
than that...
Doing so you can decompose a cohesive problem into smaller ones easily, 
no "bigger" abstractions are needed, and if the problem calls for bigger 
abstractions then scripting is not the solution any more...

>
> People who write scripts will learn the Smalltalk expression syntax
> and collection protocol.  Then they will want to write classes, so
> they will learn to use the image.  They will already know a lot of
> classes, so it will not be as big a shock as it is now.
>
> -Ralph
>
>
>


-- 
______________________________
Lic. Hernán A. Wilkinson
Gerente de Desarrollo y Tecnología
Mercap S.R.L.
Tacuari 202 - 7mo Piso - Tel: 54-11-4878-1118
Buenos Aires - Argentina
http://www.mercapsoftware.com
--------------------------------------------------------------------- 
Este mensaje es confidencial. Puede contener informacion amparada 
por el secreto profesional. Si usted ha recibido este e-mail por error, 
por favor comuniquenoslo inmediatamente via e-mail y tenga la 
amabilidad de eliminarlo de su sistema; no debera copiar el mensaje 
ni divulgar su contenido a ninguna persona. Muchas gracias. 
 
This message is confidential. It may also contain information that is 
privileged or otherwise legally exempt from disclosure. If you have 
received it by mistake please let us know by e-mail immediately and 
delete it from your system; you should also not copy the message nor 
disclose its contents to anyone. Thanks. 
 --------------------------------------------------------------------- 




More information about the Squeak-dev mailing list