Optional parameter requests - any more?

[kenmo]

Another low-priority request

Over the years, many mandatory parameters have become optional, where it makes sense.

Here are some common functions with parameters that (I believe) could be made optional! (Usually default to 0 or "").

This would not be a functional change. Just a change for cleaner code. Feel free to suggest more!


EDIT: This is about just converting mandatory parameters to optional.
Not to be confused with this other active thread about leaving parameters in the middle of the list empty when calling, to use their defaults:
http://www.purebasic.fr/english/viewtop ... =3&t=60551

Code: Select all

Date

Currently the Date function either needs 0 parameters (returns the current timestamp) or 6 parameters (Year Month Day Hour Minute Second). It would be nice if you could use 3 parameters - often I specify a date by Year/Month/Day with the rest set to 0.

Code: Select all

ExamineDirectory

Pattern$ could default to ""

Code: Select all

ReadPreferenceDouble
ReadPreferenceFloat
ReadPreferenceInteger
ReadPreferenceLong
ReadPreferenceQuad
ReadPreferenceString

The DefaultValue parameters could default to 0 or ""

Code: Select all

CreateThread

The *Value parameter could default to #Null

Code: Select all

FontRequester

The Flags parameter could default to #Null. Maybe all the parameters (FontName and FontSize) could have defaults too, like ColorRequester?

Code: Select all

InputRequester

DefaultString could default to ""

Code: Select all

OpenFileRequester
SaveFileRequester

PatternPosition could default to 0

[deesko]

This one is a lot more useful than the other idea, and cleaner too. I second this.

[Little John]

+1

[es_91]

+50

[c4s]

To the listing above I would also add the other functions of the Date library:

Code: Select all

Day
DayOfWeek
DayOfYear
FormatDate
Hour
Minute
Month
Second
Year

Similar to Date(), not specifying the parameter would simply use the current date and time. (Already requested here.)

[kenmo]

I would like to add:

Code: Select all

ScintillaGadget

Callback could default to #Null

Code: Select all

StringGadget

Content$ could default to ""


I don't know how optional parameters are implemented by the PB libraries... but if it is a pain to convert all these, then it's not really necessary.

[Blue]

my suggestion :

Code: Select all

Debug

Default could be "".
So, "Debug" by itself would output a blank line,
not ring a bell, nor display an Alert telling you that you screwed up again !

At present I use

Code: Select all

Macro Debugg
  Debug ""
EndMacro

to achieve this purpose

[kenmo]

One more to add...

I think the Options parameter of SortList() and SortArray() could reasonably default to #PB_Sort_Ascending.

[davido]

+ 1

[sancho2]

MessageRequester()
There is no need for any parameters.

[bbanelli]

MessageRequester()
There is no need for any parameters.

That would be, like, the most useful message ever.

[Thunder93]

What I like about it is it's very comprehensiveness, and so simplistic. Like trusting the words of car dealerships and wanting you to just sign on the dotted line. I don't need to know what it's about, just click OK.

MessageRequester()
There is no need for any parameters.

That would be, like, the most useful message ever.

[Dude]

A blank MessageRequester is actually a good way to pause your app during debugging (outside of the IDE).

[Little John]

What I like about it is it's very comprehensiveness, and so simplistic. Like trusting the words of car dealerships and wanting you to just sign on the dotted line. I don't need to know what it's about, just click OK.

[sancho2]

That would be, like, the most useful message ever.

LOL,

I use a blank msgbox often during debugging as was mentioned.
I would also link this request with the "skip-optional parameters request". For example:

Code: Select all

MessageRequester(,"hello")

As well as the "shorten the name of the MessageRequester function request" (to maybe MsgBox?). But I'm drifting off topic now.