Multiline comments in INI-files

Next topic

Author	Message
Peter Rudolfsen	Thursday 12 August 2010 2:23:21 am From what I know, this is not supported today. Is there any reason for this? It's probably quite easy to implement, and it would allow for more flexible INI files. One of the use cases would be to have build scripts that comment out parts of the files based on where the application/installation is deployed. Example: This could be something in an INI-file. Then the build script would recognize the ?env tags, and then add a surrounding multiline comment around this block, based on what it's built for. #?env development [DebugSettings] DebugOutput=enabled #env? To this: (/* / is just an example, it really could be anything. <!-- --> could also be used) #?env development / [DebugSettings] DebugOutput=enabled */ #env? Stupid idea, or something to take a closer look at?
André R.	Thursday 12 August 2010 5:03:13 am We plan to use a different parser in the future, so we have no intent in adding features to our current regex parser that will prevent us from moving to a faster & better* / a lot faster** parsers in the future. * http://ezcomponents.org/docs/tutorials/Configuration#ini-file-format ** http://no.php.net/parse_ini_file eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom

Author

Message

Thursday 12 August 2010 2:23:21 am

From what I know, this is not supported today. Is there any reason for this? It's probably quite easy to implement, and it would allow for more flexible INI files.

One of the use cases would be to have build scripts that comment out parts of the files based on where the application/installation is deployed.

Example:

This could be something in an INI-file. Then the build script would recognize the ?env tags, and then add a surrounding multiline comment around this block, based on what it's built for.

#?env development
 [DebugSettings]
 DebugOutput=enabled
 #env?

To this: (/* */ is just an example, it really could be anything.  could also be used)

#?env development
 /*
 [DebugSettings]
 DebugOutput=enabled
 */
 #env?

Stupid idea, or something to take a closer look at?

André R.

Thursday 12 August 2010 5:03:13 am

We plan to use a different parser in the future, so we have no intent in adding features to our current regex parser that will prevent us from moving to a faster & better* / a lot faster** parsers in the future.

* http://ezcomponents.org/docs/tutorials/Configuration#ini-file-format
** http://no.php.net/parse_ini_file

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

eZ debug

Timing:	Jan 18 2025 04:15:59
Script start
Timing:	Jan 18 2025 04:15:59
Module start 'layout'
Timing:	Jan 18 2025 04:15:59
Module start 'content'
Timing:	Jan 18 2025 04:15:59
Module end 'content'
Timing:	Jan 18 2025 04:15:59
Script end

Main resources:

Total runtime	0.6351 sec
Peak memory usage	4,096.0000 KB
Database Queries	55

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0059	587.9141	152.6250
Module start 'layout'	0.0059	0.0031	740.5391	39.4609
Module start 'content'	0.0091	0.6232	780.0000	529.0781
Module end 'content'	0.6323	0.0027	1,309.0781	8.1641
Script end	0.6350		1,317.2422

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0046	0.7188	16	0.0003
Check MTime	0.0015	0.2309	16	0.0001
Mysql Total
Database connection	0.0007	0.1104	1	0.0007
Mysqli_queries	0.5862	92.3121	55	0.0107
Looping result	0.0005	0.0847	53	0.0000
Template Total	0.6056	95.4	2	0.3028
Template load	0.0022	0.3387	2	0.0011
Template processing	0.6034	95.0172	2	0.3017
Template load and register function	0.0002	0.0283	1	0.0002
states
state_id_array	0.0008	0.1272	1	0.0008
state_identifier_array	0.0009	0.1461	2	0.0005
Override
Cache load	0.0018	0.2838	18	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.1041	2	0.0003
Fetch class attribute name	0.0014	0.2176	3	0.0005
XML
Image XML parsing	0.0006	0.0949	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0012	3	0.0000
General
dbfile	0.0008	0.1217	17	0.0000
String conversion	0.0000	0.0015	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
2	content/datatype/view/ezxmltags/link.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/link.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 15 Number of unique templates used: 8

Time used to render debug report: 0.0001 secs