# Write to socket -- does it strip quotes? **URL:** \ **Category:** Help!\ **Created:** [February 22, 2020, 8:40pm UTC](https://swi-prolog.discourse.group/t/write-to-socket-does-it-strip-quotes/1905 "2020-02-22T20:40:41Z")\ **Posts on this page:** 1\ **Showing post:** 15
**Author:** ![EricGT](https://avatars.discourse-cdn.com/v4/letter/e/f1d935/32.png) [@EricGT](https://swi-prolog.discourse.group/u/EricGT)\ **Post date:** [February 23, 2020, 11:19am UTC](https://swi-prolog.discourse.group/t/write-to-socket-does-it-strip-quotes/1905/15 "2020-02-23T11:19:08Z")
> [@Boris](#): > > how exactly do you use this flag in a module with DCGs? To understand my reasoning behind what I do requires a bit of a history lesson. When I started expanding my use of Prolog by going from just a few short exercise cases that were less than a hundred lines to to code that would work on a real world problem with multiple files I turned to using SWI-Prolog and asking questions on StackOverflow. Turns out that using StackOverflow examples to learn DCGs with SWI-Prolog for parsing will give you lots of headaches because SWI-Prolog uses double quotes differently. [The string type and its double quoted syntax](https://www.swi-prolog.org/pldoc/man?section=strings) So many of the examples for DCGs for parsing on StackOverflow and in many blogs, etc. don’t mention this and thus parse differently. If you take that code as is and try in on SWI-Prolog it sometimes works, and sometimes fails. So after many months came to realize that to ensure that my DCGs were parsing as I expected I would add ```prolog :- set_prolog_flag(double_quotes, ). :- set_prolog_flag(back_quotes, ). ``` in all the code, even the code I created, copied from StackOverflow or other places, and answer I would give on StackOverflow, and even if it was not really changing the meaning. Then as time went on I started using test cases with ```prolog :- begin_tests(abc). :- end_tests(abc). ``` and that started a second set of problems because I did not know that ```prolog :- begin_tests(abc). :- end_tests(abc). ``` are actually creating a new module and the flags are scoped to a module. So now any time I write a DCG for use by others I follow these steps. 1. Create a module using `module/2` 2. Set Prolog flags for `double_quotes` and `back_quotes` at the top of the module. 3. Add the DCGs 4. Create unit test section with `begin_tests/1` and `end_tests/1` 5. Set Prolog flags for `double_quotes` and `back_quotes` in the test section at the top of the section. 6. Add the tests. Example: [How to use DCG in Prolog](https://stackoverflow.com/a/60298371/1243762). See the variation with `module/2` * * * Another place you have to be concerned about all of this but I have yet to reason it all out is when you are developing code using the top-level and using [assert/N](https://www.swi-prolog.org/pldoc/man?predicate=assert/1) to add the predicates. How does all of this work since you are probably not using modules. To avoid that problem I write all of my code the traditional way with files, an editor and then [consult](https://www.swi-prolog.org/pldoc/man?predicate=consult/1)/[make](https://www.swi-prolog.org/pldoc/man?predicate=make/0) to load the files. * * * Related Q&A [What type is a single quoted string?](https://swi-prolog.discourse.group/t/what-type-is-a-single-quoted-string/1102) [Prolog DCG set\_prolog\_flag double\_quotes source code directive location matters; documentation?](https://stackoverflow.com/questions/45390050/prolog-dcg-set-prolog-flag-double-quotes-source-code-directive-location-matters) * * * > [@Boris](#): > > What problems do you run into? With regards to the Prolog flags `double_quotes` and `back_quotes`, none now. There are many other problems in the area related to parsing with DCGs, but I could write a few chapters on that. --- _[View the full topic](https://swi-prolog.discourse.group/t/write-to-socket-does-it-strip-quotes/1905)._