On Fri, 01 Mar 2002 19:19:37 +0200, Antti Koivunen <[EMAIL PROTECTED]> wrote:
> Stefano Mazzocchi wrote: > > Ovidiu Predescu wrote: > <skip/> > >>>>Built-in datatypes are numbers, arrays, dictionaries and function > >>>>objects. There is a special type 'void', that has a single possible > >>>>value named 'void'. > >>>> > >>>What about 'strings', 'dates' and the like? > >>> > >>Oh, yes, those too ;-) I forgot about them. > >> > > > > ok, I would add 'currency', since web-oriented flow languages will sure > > have to deal with strings, dates and money. And having them explicitly > > declared in the language might allow us to obtain 'easy' transparent > > handling (say, automatic money conversion) > > > > Are there any other 'first class concepts' that you guys might want to > > have in a flow language? IDs (as for credit-card numbers) might be > > another one, even if probably a concept too detailed... ok, your turn > > people :) > > I would think carefully before adding datatypes to any weakly typed > language. As the flow language allows easy integration with Java, I'd > recommend using standard Java classes (e.g. 'java.util.Date' and > 'java.util.Currency'), because they are the ones your custom classes are > likely to use. Yes, I think Antti is right. There is no need to define data types in the language, other than those that have an explicit syntax associated with them, e.g. numbers, strings, arrays, dictionaries and functions (did I forget anything?). For all the others the Java language implementation provides a rich and extensible collection of classes, which turn into data types in our language. So no need for currency, EJBs and anything like this which could be found in the Java language. Greetings, -- Ovidiu Predescu <[EMAIL PROTECTED]> http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
