HTTP/1.1 -1 Read error in cache disk data: SuccessContent-Type: text/csv; charset="utf-8" Last-Modified: Sat, 22 Jan 2022 07:04:43 GMT Content-length: 1300 Connection: Close Proxy-Connection: Close X-Cache: HIT from web1.osuosl.org Server: ProxyTrack 0.5 (HTTrack 3.49.2) id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,lang,patch,platform 745,Make `newclass ` and `newclass ` consistent,Austin_Hastings,,"(I have marked this ""bug"" because a reading of the code suggests the behaviors are already in agreement. But see the attached file to show otherwise.) Creating a class via `newclass ` {{{ $P0 = newclass 'Dog' }}} does not add methods from the namespace. While creating the same class via `newclass ` {{{ .local pmc class_info class_info = new 'Hash' class_info['name'] = 'Dog' $P0 = newclass class_info }}} will cause the namespace to be scanned for methods (if the PMC passes a series of validations). In fact, the documentation for `newclass` states that it accepts an optional PMC with init info: `newclass , `, but this is unsupported in the ops. I believe the current behavior is acceptable, but the and versions should behave the same w.r.t. harvesting methods from the namespace. (Alternatively, if there is to be a variant that does not scan for methods, it should be the version under the control of a configuration setting in the PMC.)",bug,closed,minor,,none,1.2.0,low,wontfix,"newclass,pmc,class",,,,linux