We have started with the enum implementation and it would be interesting to
find out what you (anyone) think should be supported and how it should be
expressed.
I have been doing some prototyping of the DSL syntax. What do you think
about this?
Simple enum:
ValueObject Weather {
Date day;
- @WeatherClassification classification;
}
enum WeatherClassification {
SUNNY, WINDY, CLOUDY;
}
Enum with attribute:
ValueObject Weather {
Date day;
- @WeatherClassification classification;
- @WindSpeed wind;
}
enum WindSpeed {
int beaufortNumber;
CALM(beaufortNumber="1"),
STORM(beaufortNumber="10"),
HURRICAN(beaufortNumber="12");
}
Enum with several attributes:
ValueObject Weather {
Date day;
- @WeatherClassification classification;
- @WindSpeed wind;
}
enum WindSpeed {
int beaufortNumber;
double minMps;
double maxMps;
CALM(beaufortNumber="1",
minMps="0",
maxMps="0.2"),
STORM(beaufortNumber="10",
minMps="24.5",
maxMps="28.4"),
HURRICAN(beaufortNumber="12",
minMps="32.7",
maxMps="40.8");
}
--
View this message in context:
http://www.nabble.com/Enums-tp13922588s17564p14425980.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Fornax-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fornax-developer
