BOOT-PRINT and LOUD-PRINT functions unnecessary

[Siskin-Bot]

Submitted by: MaxV

Are the BOOT-PRINT and LOUD-PRINT functions necessary?

I think that they are not necessary, it's a simple print, since:

boot-print: function [ 
    "Prints during boot when not quiet."
    data][ unless system/options/quiet [print :data] ] 

Nobody needs it.
You can replace it during boot with:

unless system/options/quiet [print data]

unless system/options/quiet [print data]

---

^{Imported from: CureCode [ Version: 2.101.0 Type: Bug Platform: All Category: Mezzanine Reproduce: Always Fixed-in:none ]
Imported from: metaeducation#1920}

Comments:

Rebolbot commented on Jan 4, 2013:

Submitted by: abolka

It is used repeatedly in boot/startup code, and I see no good reason for eliminating it from startup code.

However, if possible, boot-print should probably be made internal to the startup code, and not leak through into the default user context.

---

Rebolbot commented on Jan 4, 2013:

Submitted by: MaxV

Yes, please unset it after boot!

---

Rebolbot commented on Jan 4, 2013:

Submitted by: BrianH

It would be better to move LOUD-PRINT and BOOT-PRINT to the sys context, or some other private context, than to unset them. We don't want extra words defined in the lib or user contexts, even if they're unset.

However, I'm not sure that these functions are unnecessary after boot. LOUD-PRINT is used when loading extensions, and BOOT-PRINT is used in DO. It may be the case that these functions may not be needed at all, or that they should be moved to sys, but they are still used.

For that matter, LOUD-PRINT is meant to be used by user scripts/modules that want to put more information out there when R3 is started in verbose mode. BOOT-PRINT is meant to for code that needs to provide less information when R3 is started in quiet mode. User code often has to do the same things that mezzanine code does, for the same reasons.

---

Rebolbot commented on Jan 6, 2013:

Submitted by: BrianH

Merged the LOUD-PRINT ticket and deleted it.

---

Rebolbot added the Type.bug on Jan 12, 2016

---