Menu

#637 Schedule comments

Version 4.0 RC1
assigned
None
wontfix
none
none
trunk
enhancement
2016-05-15
2012-11-26
No

The current schedule system uses both // and # for comments. Though based on the cron format, it seems superfluous to use two different tokens for comments.
Removing the use of # for comments in schedules would prevent programatically defined schedules from using comments ~ though those schedules to use C-style comments outside the strings. The token would also be 'cleaned up' within the GLM syntax, focusing its use on macros.

Discussion

  • David P. Chassin

    • milestone changed from Unscheduled to Version 3.0 RC 1
     
  • David P. Chassin

    • status changed from new to assigned
     
  • David P. Chassin

    • owner changed from dchassin to jcfuller

    Not sure we want to do this. Please confirm if desired.

     
  • Jason Fuller

    Jason Fuller - 2014-08-08
    • Description has changed:

    Diff:

    
    
    • Resolution: --> wontfix
    • Component: Core --> none
    • Priority: trivial --> none
     
  • Jason Fuller

    Jason Fuller - 2014-08-08

    Let's leave this alone for backwards compatibility.

     
  • David P. Chassin

    • Owner: Jason Fuller --> David P. Chassin
    • Milestone: Version 3.0 RC 1 --> Unscheduled
     
  • David P. Chassin

    • Milestone: Unscheduled --> Version 4.0 RC1