Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

Rebol Bug-List

 [1/12] from: al:bri:xtra at: 13-Oct-2000 4:09


Hi, Ladislav. I'm replying through the Rebol list, because my ISP says: <Quote> This Message was undeliverable due to the following reason: Your message was not delivered because the return address was refused. The return address was '<[Al--Bri--xtra--co--nz]>' </Quote> It seems your email service doesn't like me. :-( You wrote (directly to me):
> How about the bug list organization - all bugs in one file, or a file for
every bug? One bug = one file. One file to list them, one file to describe them, and one file to link them all! :-) Apart from sounding like a line from Tolkien, it's a reasonable plan I believe. Suggestions Directories like this: /Core /View /Apache /Command Each of the above having: /New - This is for new bugs. /Fixing - Bugs being fixed (hopefully). /Fixed - For fixed bugs. [Your suggestions here.] Andrew Martin ICQ: 26227169 http://members.nbci.com/AndrewMartin/

 [2/12] from: petr:krenzelok:trz:cz at: 13-Oct-2000 13:17


[Al--Bri--xtra--co--nz] wrote:
> Hi, Ladislav. > I'm replying through the Rebol list, because my ISP says:
<<quoted lines omitted: 21>>
> /Fixing - Bugs being fixed (hopefully). > /Fixed - For fixed bugs.
Seem to be fine strategy, as it comply with your component/plug-in/enhancement/patch system. Btw: any progress here? :-) -pekr-
> [Your suggestions here.] >
you should buy me a beer ;-)

 [3/12] from: joel:neely:fedex at: 13-Oct-2000 6:55


[Al--Bri--xtra--co--nz] wrote:
> One bug = one file. One file to list them, one file to describe them, and > one file to link them all! :-)
<<quoted lines omitted: 11>>
> /Fixed - For fixed bugs. > [Your suggestions here.]
Does the /New /Fixing /Fixed trichotomy imply that a bug report would migrate between directories as its status changes? This would imply that I couldn't, for example, bookmark a bug report and return periodically (or via a REBOL 'bot ;-) to check for changes in status. Would it be simpler to have a "status" datum for each report, and have a variety of list/link files to categorize them in various useful ways (platform, status, who reported, version in which it appeared, version in which it was exterminated...)? -jn-

 [4/12] from: al:bri:xtra at: 13-Oct-2000 5:09


pekr wrote:
> Andrew wrote: > > Each of the above having:
<<quoted lines omitted: 3>>
> > > Seem to be fine strategy, as it comply with your
component/plug-in/enhancement/patch system.
> Btw: any progress here? :-)
Still working on system. I've realised I need a simpler system to store them to my site, and to retrieve them from other locations.
> > [Your suggestions here.] > you should buy me a beer ;-)
======================================= | This voucher permits the bearer: | | one (1) beer | | at any virtual bar on the internet. | | Signed: Andrew Martin. | ======================================= Andrew Martin ICQ: 26227169 http://members.nbci.com/AndrewMartin/

 [5/12] from: petr:krenzelok:trz:cz at: 13-Oct-2000 14:15


[Al--Bri--xtra--co--nz] wrote:
> pekr wrote: > > Andrew wrote:
<<quoted lines omitted: 9>>
> Still working on system. I've realised I need a simpler system to store them > to my site, and to retrieve them from other locations.
What's the problem with storage? /components/component-name.r's header contains 'home or 'file, the fields to store the storage, e.g. www.somesite.com/rebol/components/component-name.r. Or are you talking about anything else?
> > > [Your suggestions here.] > > you should buy me a beer ;-)
<<quoted lines omitted: 3>>
> | Signed: Andrew Martin. | > >
:-))) Well, thanks, I will enjoy it. Anyone to join me? :-)

 [6/12] from: sharriff:aina:med-iq at: 13-Oct-2000 13:49


Hi Guys! Ive seen The word "does" a few times with objects. Can somone tell me where to look up info on it? its not in the core dictionary or users guide. Sharriff Aina med.iq information & quality in healthcare AG

 [7/12] from: petr:krenzelok:trz:cz at: 13-Oct-2000 15:11


[Sharriff--Aina--med-iq--de] wrote:
> Hi Guys! > > Ive seen The word "does" a few times with objects. Can somone tell me > where to look up info on it? its not in the core dictionary or users guide. >
->> source does does: func [ {Defines a function that has no arguments or locals.} [catch] body [block!] "The body block of the function" ][ throw-on-error [make function! [] body] ] ->>

 [8/12] from: lmecir:geocities at: 13-Oct-2000 15:41


Hi, I don't understand, why your mail didn't get through (I received your previous mail normally).
> Hi, Ladislav. > I'm replying through the Rebol list, because my ISP says:
<<quoted lines omitted: 6>>
> You wrote (directly to me): > > How about the bug list organization - all bugs in one file, or a file
for
> every bug? > One bug = one file. One file to list them, one file to describe them, and
<<quoted lines omitted: 12>>
> /Fixed - For fixed bugs. > [Your suggestions here.]
How about /Patched?

 [9/12] from: sharriff:aina:med-iq at: 13-Oct-2000 14:42


Isnt this the same as defining an unamed function without arguments? Sharriff Aina med.iq information & quality in healthcare AG Gutenbergstr. 42 41564 Kaarst tel.: 02131-3669-0 fax: 02131-3669-599 www.med-iq.de Petr.Krenzelo [k--trz--cz] An: [list--rebol--com] Kopie: 13.10.00 Thema: [REBOL] Antwort: Rebol Bug-List Re:(3) 14:11 Bitte antworten an list [Sharriff--Aina--med-iq--de] wrote:
> Hi Guys! > > Ive seen The word "does" a few times with objects. Can somone tell me > where to look up info on it? its not in the core dictionary or users
guide.
->> source does does: func [ {Defines a function that has no arguments or locals.} [catch] body [block!] "The body block of the function" ][ throw-on-error [make function! [] body] ] ->>

 [10/12] from: joel:neely:fedex at: 13-Oct-2000 11:58


Hello, Sharriff,
>> ? does
USAGE: DOES body DESCRIPTION: Defines a function that has no arguments or locals. DOES is a function value. ARGUMENTS: body -- The body block of the function (Type: block) (SPECIAL ATTRIBUTES) catch
>> greet: does [print "Hi, Sharriff"] >> greet
Hi, Sharriff
>>
[Sharriff--Aina--med-iq--de] wrote:
> Hi Guys! > > Ive seen The word "does" a few times with objects. Can somone tell me > where to look up info on it? its not in the core dictionary or users guide. > > Sharriff Aina > med.iq information & quality in healthcare AG
-- ; Joel Neely [joel--neely--fedex--com] 901-263-4460 38017/HKA/9677 REBOL [] do [ do func [s] [ foreach [a b] s [prin b] ] sort/skip do function [s] [t] [ t: "" foreach [a b] s [repend t [b a]] t ] { | e s m!zauafBpcvekexEohthjJakwLrngohOqrlryRnsctdtiub} 2 ]

 [11/12] from: joel:neely:fedex at: 13-Oct-2000 12:10


Hi, Sharriff, [Sharriff--Aina--med-iq--de] wrote:
> Isnt this the same as defining an unamed function without arguments? > Sharriff Aina
<<quoted lines omitted: 4>>
> fax: 02131-3669-599 > www.med-iq.de
Yes.
>> source does
does: func [ {Defines a function that has no arguments or locals.} [catch] body [block!] "The body block of the function" ][ throw-on-error [make function! [] body] ] The same effect can be obtained a couple of ways.
>> greet: does [print "Hi, Sharriff"] >> greet
Hi, Sharriff
>> greet: to-paren [print "Hi, Sharriff"]
== (print "Hi, Sharriff")
>> greet
Hi, Sharriff
>> greet: func [] [print "Hi, Sharriff"] >> greet
Hi, Sharriff
>> greeting: [print "Hi, Sharriff"]
== [print "Hi, Sharriff"]
>> do greeting
Hi, Sharriff It would be interesting to see what tradeoffs exist among these various approaches. YMMV. -jn- -- ; Joel Neely [joel--neely--fedex--com] 901-263-4460 38017/HKA/9677 REBOL [] do [ do func [s] [ foreach [a b] s [prin b] ] sort/skip do function [s] [t] [ t: "" foreach [a b] s [repend t [b a]] t ] { | e s m!zauafBpcvekexEohthjJakwLrngohOqrlryRnsctdtiub} 2 ]

 [12/12] from: g:santilli:tiscalinet:it at: 14-Oct-2000 15:48


Hello [joel--neely--fedex--com]! On 13-Ott-00, you wrote: j> Does the /New /Fixing /Fixed trichotomy imply that a bug j> report would migrate between directories as its status j> changes? This would imply that I couldn't, for example, j> bookmark a bug report and return periodically (or via a REBOL j> 'bot ;-) to check for changes in status. Moving the files across directories is not a good idea IMHO. j> Would it be simpler to have a "status" datum for each report, j> and have a variety of list/link files to categorize them in j> various useful ways (platform, status, who reported, version j> in which it appeared, version in which it was j> exterminated...)? I think so, too. Regards, Gabriele. -- Gabriele Santilli <[giesse--writeme--com]> - Amigan - REBOL programmer Amiga Group Italia sez. L'Aquila -- http://www.amyresource.it/AGI/

Notes
  • Quoted lines have been omitted from some messages.
    View the message alone to see the lines that have been omitted