You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(80) |
Jun
(71) |
Jul
(34) |
Aug
(58) |
Sep
|
Oct
(220) |
Nov
(146) |
Dec
(36) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(28) |
Feb
(152) |
Mar
(293) |
Apr
(213) |
May
(158) |
Jun
(96) |
Jul
(78) |
Aug
(39) |
Sep
(169) |
Oct
(128) |
Nov
(83) |
Dec
(149) |
2003 |
Jan
(155) |
Feb
(14) |
Mar
(60) |
Apr
(86) |
May
(92) |
Jun
(109) |
Jul
(25) |
Aug
(44) |
Sep
(10) |
Oct
(39) |
Nov
(37) |
Dec
(128) |
2004 |
Jan
(71) |
Feb
(199) |
Mar
(192) |
Apr
(360) |
May
(93) |
Jun
(75) |
Jul
(51) |
Aug
(195) |
Sep
(390) |
Oct
(186) |
Nov
(173) |
Dec
(331) |
2005 |
Jan
(102) |
Feb
(154) |
Mar
(160) |
Apr
(88) |
May
(79) |
Jun
(78) |
Jul
(126) |
Aug
(94) |
Sep
(110) |
Oct
(187) |
Nov
(188) |
Dec
(31) |
2006 |
Jan
(12) |
Feb
(40) |
Mar
(123) |
Apr
(102) |
May
(62) |
Jun
(36) |
Jul
(19) |
Aug
(31) |
Sep
(59) |
Oct
(67) |
Nov
(57) |
Dec
(35) |
2007 |
Jan
(153) |
Feb
(53) |
Mar
(27) |
Apr
(11) |
May
(49) |
Jun
(3) |
Jul
(56) |
Aug
(58) |
Sep
(30) |
Oct
(57) |
Nov
(47) |
Dec
(155) |
2008 |
Jan
(71) |
Feb
(68) |
Mar
(79) |
Apr
(72) |
May
(82) |
Jun
(10) |
Jul
(19) |
Aug
(25) |
Sep
(17) |
Oct
(10) |
Nov
(32) |
Dec
(9) |
2009 |
Jan
(26) |
Feb
(1) |
Mar
(1) |
Apr
(12) |
May
(16) |
Jun
(7) |
Jul
(12) |
Aug
(22) |
Sep
(21) |
Oct
|
Nov
(7) |
Dec
|
2010 |
Jan
(3) |
Feb
(3) |
Mar
(1) |
Apr
|
May
(5) |
Jun
(5) |
Jul
|
Aug
|
Sep
(4) |
Oct
(2) |
Nov
|
Dec
(6) |
2011 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(8) |
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(8) |
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
(11) |
Mar
(1) |
Apr
(4) |
May
|
Jun
|
Jul
(2) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
(5) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(2) |
Dec
(1) |
2015 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
2016 |
Jan
(8) |
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
2017 |
Jan
(3) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2018 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2022 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Eric B. <er...@go...> - 2008-01-12 09:51:25
|
Colin Paul Adams wrote: > I notice that whereas ise will launch multiple jobs to compile > generated C code, gec appears to only launch one - resulting in long > compile times. > > Is this inherent in the process, or is it due to my command line: No work has been done to let gec compile several C files concurrently. Currently it is a mere script compiling the C files one after the other. No work has been done either on trying to make the C code generation incremental, and hence avoiding having to recompile C code that has not changed between two successive compilations. And no effort has been made to try to make the generated C code as optimized as possible. There are plenty of areas where gec can be improved. Which means that there is room to make gec even better in the near future. Currently my focus is more on the Eiffel part, trying to make it more compliant with ISE Eiffel and more generally with ECMA/ISO Eiffel. -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |
From: Colin P. A. <co...@co...> - 2008-01-11 17:03:48
|
I notice that whereas ise will launch multiple jobs to compile generated C code, gec appears to only launch one - resulting in long compile times. Is this inherent in the process, or is it due to my command line: gec --finalize --cc=yes --catcall=error --gc=boehm compile_ge.ace -- Colin Adams Preston Lancashire |
From: Colin P. A. <co...@co...> - 2008-01-11 14:37:50
|
>>>>> "Colin" == Colin Adams <col...@go...> writes: Colin> OK. I understand your point now. I did think at the Colin> weekend about making it a generic parameter (constrained to Colin> a descendant of NUMERIC), but then I got side-tracked by Colin> the possibility of eliminating MA_DECIMAL altogether. Colin> I will investigate this at the weekend. I've reviewed DT_XSLT_NUMBERER_EN to see whether this is possible. The main problem seems to be the use of {MA_DECIMAL}.is_integer/to_integer as NUMERIC doesn't have these. The use of {MA_DECIMAL}.to_scientific_string is also an issue - but it is probably non-conformant as it is. I can eliminate MA_DECIMAL quite easily by using a new deferred class which will have two descendants, one based on INTEGER_64 or INTEGER_32, and one based on MA_DECIMAL. But you are already unhappy about the use of auxiliary classes. And I definitely can't eliminate the unicode library usage. -- Colin Adams Preston Lancashire |
From: Colin A. <col...@go...> - 2008-01-07 14:33:19
|
On 07/01/2008, Eric Bezault <er...@go...> wrote: > > Colin Adams wrote: > > > Unfortunately, yes, it is (I did have a look into this). > > What is more, it will get worse in the future - so far there is only an > > English language version. There will be more. > > What impact would it have on the integers held in a date? > Would they use other unicode characters for the digits? That is already possible even for the English language version. The main significance of language is if you choose word output. E.g. Two Thousand and Seven (rather than 2007). > It sounds to me as if because when written to a file an integer > > and a decimal look the same we should first convert INTEGERs to > > MA_DECIMALs when passing them to class FILE. > > > > > > Now you've lost me. > > In other words, for anything I want to do in an INTEGER, why > would I need to convert it to a MA_DECIMAL first? If I dpn't > do this conversion for anything I do with an INTEGER, why should > it be different in this particular case? OK. I understand your point now. I did think at the weekend about making it a generic parameter (constrained to a descendant of NUMERIC), but then I got side-tracked by the possibility of eliminating MA_DECIMAL altogether. I will investigate this at the weekend. |
From: Eric B. <er...@go...> - 2008-01-07 14:20:05
|
Colin Adams wrote: > On 07/01/2008, *Eric Bezault* <er...@go... > <mailto:er...@go...>> wrote: > > Colin Adams wrote: > > > But the code is shared by xsl:number (as the formatting rules are > > defined to be the same), which might format any number. > > And is it that much code duplication to implement the formatting > rules both for an INTEGER and for a MA_DECIMAL as input? > > > Unfortunately, yes, it is (I did have a look into this). > What is more, it will get worse in the future - so far there is only an > English language version. There will be more. What impact would it have on the integers held in a date? Would they use other unicode characters for the digits? > It sounds to me as if because when written to a file an integer > and a decimal look the same we should first convert INTEGERs to > MA_DECIMALs when passing them to class FILE. > > > Now you've lost me. In other words, for anything I want to do in an INTEGER, why would I need to convert it to a MA_DECIMAL first? If I dpn't do this conversion for anything I do with an INTEGER, why should it be different in this particular case? -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |
From: Colin A. <col...@go...> - 2008-01-07 14:11:59
|
On 07/01/2008, Eric Bezault <er...@go...> wrote: > > Colin Adams wrote: > > > But the code is shared by xsl:number (as the formatting rules are > > defined to be the same), which might format any number. > > And is it that much code duplication to implement the formatting > rules both for an INTEGER and for a MA_DECIMAL as input? Unfortunately, yes, it is (I did have a look into this). What is more, it will get worse in the future - so far there is only an English language version. There will be more. It sounds to me as if because when written to a file an integer > and a decimal look the same we should first convert INTEGERs to > MA_DECIMALs when passing them to class FILE. Now you've lost me. |
From: Eric B. <er...@go...> - 2008-01-07 13:43:08
|
Colin Adams wrote: > > > On 07/01/2008, *Eric Bezault* <er...@go... > <mailto:er...@go...>> wrote: > > > BTW, how come we need such big numbers to format dates? > > We don't. > But the code is shared by xsl:number (as the formatting rules are > defined to be the same), which might format any number. And is it that much code duplication to implement the formatting rules both for an INTEGER and for a MA_DECIMAL as input? It sounds to me as if because when written to a file an integer and a decimal look the same we should first convert INTEGERs to MA_DECIMALs when passing them to class FILE. Code duplication is one thing, but wasting execution time to convert entities in one way or another just for the sake of avoiding code duplication (and introducing library dependencies during that process) in another thing that is not necessarily better. -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |
From: Colin A. <col...@go...> - 2008-01-07 13:16:18
|
On 07/01/2008, Eric Bezault <er...@go...> wrote: > > > BTW, how come we need such big numbers to format dates? > > We don't. But the code is shared by xsl:number (as the formatting rules are defined to be the same), which might format any number. |
From: Eric B. <er...@go...> - 2008-01-07 09:50:34
|
Colin Paul Adams wrote: > I got my requested clarification from the working group - the limit > only applies if the range of xs:integer is limited by the > implementation. > And it was to avoid doing this that we introduced MA_DECIMAL into Gobo > in the first place. BTW, how come we need such big numbers to format dates? -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |
From: Eric B. <er...@go...> - 2008-01-07 09:49:31
|
Colin Paul Adams wrote: > I got my requested clarification from the working group - the limit > only applies if the range of xs:integer is limited by the > implementation. > And it was to avoid doing this that we introduced MA_DECIMAL into Gobo > in the first place. I don't think that MA_DECIMAL has been introduced into Gobo to accommodate xs:integer ;-) -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |
From: Colin P. A. <co...@co...> - 2008-01-07 06:28:59
|
>>>>> "Colin" == Colin Paul Adams <co...@co...> writes: Colin> But after looking at the appendix to the XSLT Colin> recommendation, I see that an implementation is allowed to Colin> specify a maximum number that can be formatted. And as I Colin> can't see any practical use cases for formatting larger Colin> numbers than can be represented by INTEGER (the intended Colin> use case for xsl:number is for formatting section Colin> numbering, and the like), I shall have a go at eliminating Colin> the use of MA_DECIMAL. I got my requested clarification from the working group - the limit only applies if the range of xs:integer is limited by the implementation. And it was to avoid doing this that we introduced MA_DECIMAL into Gobo in the first place. So it will have to stay. -- Colin Adams Preston Lancashire |
From: Colin P. A. <co...@co...> - 2008-01-06 17:07:36
|
>>>>> "Eric" == Eric Bezault <er...@go...> writes: >> Well, I won't be able to remove any dependency on structure Eric> Do you know where this dependency on structure comes from? DT_XSLT_FORMAT_DATE_TIME: Lots of use of DS_CELL for passing arguments. These could be changed to KL_CELL. Two uses of ST_SPLITTER/DS_LIST for parsing values (that seems to be the string library). Since the splitting is only on a single character, I guess it wouldn't be a big job after all to remove this, BUT: DT_XSLT_NUMBER_ROUTINES: This has string/unicode dependencies only - these are vital, and can not be removed. And including this library is a much larger overhead than anything else we have been talking about. -- Colin Adams Preston Lancashire |
From: Eric B. <er...@go...> - 2008-01-06 16:26:38
|
Colin Paul Adams wrote: >>>>>> "Eric" == Eric Bezault <er...@go...> writes: > > >> Well this isn't new. If you look at the system.xace in the > >> test/time directory, you will see quite a few dependencies. > >> Mind you, some of them may just be for the test framework. > > Eric> Yes, there are for the test framework. I had to add them in > Eric> example/time/clock. > > Well, I won't be able to remove any dependency on structure Do you know where this dependency on structure comes from? -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |
From: Colin P. A. <co...@co...> - 2008-01-06 16:20:24
|
>>>>> "Eric" == Eric Bezault <er...@go...> writes: >> Well this isn't new. If you look at the system.xace in the >> test/time directory, you will see quite a few dependencies. >> Mind you, some of them may just be for the test framework. Eric> Yes, there are for the test framework. I had to add them in Eric> example/time/clock. Well, I won't be able to remove any dependency on structure (so I might as well forget about removing the dependency on math, although I will still do it if I can, as it slows down execution a lot). -- Colin Adams Preston Lancashire |
From: Eric B. <er...@go...> - 2008-01-06 16:04:59
|
Colin Paul Adams wrote: >>>>>> "Eric" == Eric Bezault <er...@go...> writes: > > Eric> Colin Paul Adams wrote: > >> I shall have a go at eliminating the use of MA_DECIMAL. > > Eric> Great. Also note that my experience, running the Gobo > Eric> bootstrap and test suite with ISE, showed that in addition > Eric> to regexp and math, the date/time library now also depends > Eric> on library/string and library/structure. > > Well this isn't new. If you look at the system.xace in the test/time > directory, you will see quite a few dependencies. > Mind you, some of them may just be for the test framework. Yes, there are for the test framework. I had to add them in example/time/clock. -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |
From: Colin P. A. <co...@co...> - 2008-01-06 16:03:52
|
>>>>> "Eric" == Eric Bezault <er...@go...> writes: Eric> Colin Paul Adams wrote: >> Here is advanced notice that I have started preliminary work >> (since Christmas, actually) on a regular expression library for >> use with Unicode text. It will support muliple dialects for >> regular expression languages (the initial implementation will >> support the XPath and XML Schema regular expression >> languages. My need is for the former, but it is a superset of >> the latter, so I might as well do both at once). >> >> It will be at least a month before I have anything worth >> looking at. Eric> OK. Does that mean that there will be a new dependency on Eric> library/string to have access to its unicode cluster? Well, that will depend where we decide to put it. Since I am messing about with the design a lot, I wanted to check it in to experimental (just so I can look back at my experiments in case I delete something and decide I want it after all). But this doesn't exist in the svn version. So I'm checking in to the gestalt sourceforge site (as that is a set of programs rather than a library, it isn't a problem for me). Then when I have something working, I shall ask for a preliminary assesment, comments on the approach (I shall be using 0-127 - as indices into a state transition for ASCII characters, as 128+ to represent character classes. Hopefully that way we can maintain performance for ASCII, whilst still accomodaing full Unicode compatibility, and reasonable size tables) and design (does anyone know of any papers in this area?). After that, I'll do any necessary re-working, and we can decide on a library structure. -- Colin Adams Preston Lancashire |
From: Colin P. A. <co...@co...> - 2008-01-06 15:59:16
|
>>>>> "Eric" == Eric Bezault <er...@go...> writes: Eric> Colin Paul Adams wrote: >> I shall have a go at eliminating the use of MA_DECIMAL. Eric> Great. Also note that my experience, running the Gobo Eric> bootstrap and test suite with ISE, showed that in addition Eric> to regexp and math, the date/time library now also depends Eric> on library/string and library/structure. Well this isn't new. If you look at the system.xace in the test/time directory, you will see quite a few dependencies. Mind you, some of them may just be for the test framework. -- Colin Adams Preston Lancashire |
From: Eric B. <er...@go...> - 2008-01-06 15:58:07
|
Colin Paul Adams wrote: > Here is advanced notice that I have started preliminary work (since > Christmas, actually) on a regular expression library for use with > Unicode text. It will support muliple dialects for regular expression > languages (the initial implementation will support the XPath and XML > Schema regular expression languages. My need is for the former, but it > is a superset of the latter, so I might as well do both at once). > > It will be at least a month before I have anything worth looking at. OK. Does that mean that there will be a new dependency on library/string to have access to its unicode cluster? -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |
From: Colin P. A. <co...@co...> - 2008-01-06 15:56:18
|
>>>>> "Colin" == Colin Paul Adams <co...@co...> writes: Colin> But after looking at the appendix to the XSLT Colin> recommendation, I see that an implementation is allowed to Colin> specify a maximum number that can be formatted. Unfortunately this appendix is non-normative. There may or may not be a contradiction with the body of the recommendation. I am seeking a ruling from the working group. -- Colin Adams Preston Lancashire |
From: Eric B. <er...@go...> - 2008-01-06 15:55:56
|
Colin Paul Adams wrote: > I shall have a go at eliminating the use of MA_DECIMAL. Great. Also note that my experience, running the Gobo bootstrap and test suite with ISE, showed that in addition to regexp and math, the date/time library now also depends on library/string and library/structure. -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |
From: Colin P. A. <co...@co...> - 2008-01-06 15:55:06
|
>>>>> "Eric" == Eric Bezault <er...@go...> writes: Eric> Colin Paul Adams wrote: >>>>>>> "Colin" == Colin Paul Adams <co...@co...> >>>>>>> writes: >> Colin> I can eliminate the regular expression without too much Colin> trouble. >> >> I've done that now. Eric> OK, thanks. Eric> Note that I had already started the process necessary to Eric> check-in the snapshot of Gobo at AXAR. Do you want me to Eric> start again from scratch? It's not a big deal for me, it's Eric> just that it would delay the process by one day or so. Just Eric> let me know. No it doesn't make any difference. The next check-in will just remove the dependency silently, and won't make any difference. -- Colin Adams Preston Lancashire |
From: Eric B. <er...@go...> - 2008-01-06 15:53:41
|
Colin Paul Adams wrote: >>>>>> "Colin" == Colin Paul Adams <co...@co...> writes: > > Colin> I can eliminate the regular expression without too much > Colin> trouble. > > I've done that now. OK, thanks. Note that I had already started the process necessary to check-in the snapshot of Gobo at AXAR. Do you want me to start again from scratch? It's not a big deal for me, it's just that it would delay the process by one day or so. Just let me know. -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |
From: Colin P. A. <co...@co...> - 2008-01-06 11:23:49
|
Here is advanced notice that I have started preliminary work (since Christmas, actually) on a regular expression library for use with Unicode text. It will support muliple dialects for regular expression languages (the initial implementation will support the XPath and XML Schema regular expression languages. My need is for the former, but it is a superset of the latter, so I might as well do both at once). It will be at least a month before I have anything worth looking at. -- Colin Adams Preston Lancashire |
From: Colin P. A. <co...@co...> - 2008-01-06 11:20:19
|
>>>>> "Colin" == Colin Paul Adams <co...@co...> writes: Colin> Eliminating the use Colin> of MA_DECIMAL will be much harder - it can be done, but not Colin> without duplicating a lot of code. The need was because the code is also used by the implementation of xsl:number (formatting dates and times are already limited to INTEGER by virtue of DT_DATE using INTEGER for the year). But after looking at the appendix to the XSLT recommendation, I see that an implementation is allowed to specify a maximum number that can be formatted. And as I can't see any practical use cases for formatting larger numbers than can be represented by INTEGER (the intended use case for xsl:number is for formatting section numbering, and the like), I shall have a go at eliminating the use of MA_DECIMAL. -- Colin Adams Preston Lancashire |
From: Colin P. A. <co...@co...> - 2008-01-06 10:28:43
|
>>>>> "Colin" == Colin Paul Adams <co...@co...> writes: Colin> I can eliminate the regular expression without too much Colin> trouble. I've done that now. -- Colin Adams Preston Lancashire |