NuSphere Forums Forum Index
NuSphere Forums
Reply to topic
Strings


Joined: 15 Aug 2003
Posts: 44
Reply with quote
http://www.php.net/manual/en/language.types.string.php#language.types.string.parsing

http://www.php.net/manual/en/language.types.string.php#language.types.string.syntax.heredoc

1. Can you update the syntax highlighting logic according to these resources ?

2. Can we have any kind of controls over the syntax highlighting logic ?
View user's profileFind all posts by Post-O-MaticSend private message


Joined: 15 Aug 2003
Posts: 44
Reply with quote
No comments ?

Even a simple "yes/no" would suffice... Confused
View user's profileFind all posts by Post-O-MaticSend private message
Site Admin

Joined: 13 Jul 2003
Posts: 7861
Reply with quote
Quote:
1. Can you update the syntax highlighting logic according to these resources ?

yes it's possible in a future version.

Quote:
2. Can we have any kind of controls over the syntax highlighting logic ?

more no than yes. As a side effect hardcoded logic works much faster.
View user's profileFind all posts by dmitriSend private messageVisit poster's website


Joined: 15 Aug 2003
Posts: 44
Reply with quote
Any updates on the subject ? Very Happy
View user's profileFind all posts by Post-O-MaticSend private message


Joined: 21 Nov 2003
Posts: 39
Reply with quote
i support updating the heredoc highlighting scheme
also the php-style string coloring might be a bit better

ddmitrie, what about extracting the hard-coded highlighting system and put it into a DLL. then, people can switch the HL-ing themes (or make one themselves)
the HLing code isnt so specific that it should stay in the executable

_________________
-/ NetGert /-
View user's profileFind all posts by netgertSend private messageVisit poster's websiteMSN Messenger


Joined: 15 Aug 2003
Posts: 44
Reply with quote
I really don't mind that the syntax highlighting code is hardcoded if that gives a significant performance boost (Altough I'm speaking for myself here), as long as that code is kept up-to-date with the PHP syntax (which doesn't change that much, really).

I don't know how it is in other development teams, but anywhere I worked before If a certain form of syntax broke the syntax highlighting logic, all the developers neglected it. Syntax flexebility is mainly about promoting readablity, and anything that breaks the syntax highlighting usually renders the whole file unreadable, so there's no point in using it.

Therefore I simply don't use heredoc syntax, Although I would have and it would have made my code much cleaner in several places, if it wasn't breaking the syntax highlighting.


Regarding the implementation. First of you can make two syntax highlighting implementations: one that is the hardcoded compiled-in one, and the other similar to other IDEs where you have a syntax file that defines the syntax. The user can choose between the two. PHPEd would be installed with the first one as default. The second one will probably only be used by users when the hardcoded logic doesn't work, hopefully only temporary until the hardcoded logic is updated.

Second, if netgert's proposal is indeed practical in your eyes, then that is definitely something to consider. Provided that the API for the DLL is not too comlicated, this can be a marvelous solution. If PHPEd is released with the syntax highlighting logic's code open, it's very likely that changes and enhancements would take very little effort on behalf of the user.
View user's profileFind all posts by Post-O-MaticSend private message
Site Admin

Joined: 13 Jul 2003
Posts: 7861
Reply with quote
have no objections. The idea looks really good.
View user's profileFind all posts by dmitriSend private messageVisit poster's website
Strings
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All times are GMT - 5 Hours  
Page 1 of 1  

  
  
 Reply to topic